CRELEVANCELEVEL. More...
#include <CRelevanceLevel.h>
Public Member Functions | |
CRelevanceLevel () | |
just used to be able to construct emtpy elements in which to copy (STL) | |
CRelevanceLevel (const string &inURL, double inRelevanceLevel) | |
The constructor most frequently used. | |
CRelevanceLevel (const CRelevanceLevel &inElement) | |
copy constructor | |
bool | input (istream &inStream) |
binary input | |
bool | output (ostream &outStream) const |
binary output | |
bool | outputHTML (ostream &outStream) const |
output as HTML | |
string | getURL () const |
Accessors. | |
double | getRelevanceLevel () const |
void | setRelevanceLevel (const double inRelevanceLevel) |
void | adjustRelevanceLevel (const double inRelevanceLevel) |
void | divideRelevanceLevelBy (const double inDivisor) |
string | toXML () const |
CRELEVANCELEVEL.
modification history: WM 1099 changed documentation fromat HM 090399 created the documentation WM 1098 created the file
compiler defines used:
What do you think, folx? I think, that the relevance level as it is, is too inflexible. We need to reflect a bit more what is given by MRML. to be FIXME d
CRelevanceLevel::CRelevanceLevel | ( | ) |
just used to be able to construct emtpy elements in which to copy (STL)
CRelevanceLevel::CRelevanceLevel | ( | const CRelevanceLevel & | inElement | ) |
copy constructor
string CRelevanceLevel::getURL | ( | ) | const |
Accessors.
bool CRelevanceLevel::input | ( | istream & | inStream | ) |
binary input
bool CRelevanceLevel::output | ( | ostream & | outStream | ) | const |
binary output
bool CRelevanceLevel::outputHTML | ( | ostream & | outStream | ) | const |
output as HTML