Main Page   Namespace List   Class Hierarchy   Alphabetical List   Compound List   File List   Namespace Members   Compound Members   File Members   Related Pages  

MODEL::GenericProbe Class Reference

#include <probe.h>

Inheritance diagram for MODEL::GenericProbe:

Inheritance graph
[legend]
Collaboration diagram for MODEL::GenericProbe:

Collaboration graph
[legend]
List of all members.

Public Methods

 GenericProbe (TimeFrame &T, const string &fn)
 GenericProbe (TimeFrame &T, ostream &os)
 ~GenericProbe ()
virtual void tick ()
virtual void probe (void)=0
void write_data (void)
virtual void print (ostream &out)=0
 NO_COPY (GenericProbe)

Protected Attributes

string n
ostream* out

Detailed Description

The base class for probes. Probe itself is already more specialized and expects the routine to write a number of data points on every call

Definition at line 35 of file probe.h.


Constructor & Destructor Documentation

GenericProbe ( TimeFrame & T,
const string & fn )
 

Without ostream

Definition at line 27 of file probe.cpp.

GenericProbe ( TimeFrame & T,
ostream & os )
 

With ostream

Definition at line 32 of file probe.cpp.


Member Function Documentation

NO_COPY ( GenericProbe )
 

Don't copy or assign

void print ( ostream & out ) [pure virtual]
 

Implement this one to write the data. You can call it upon destruction of your derived object. Unfortunately, I have not yet figured out how to call a derived function inside a destructor (as a general rule, this is not possible: it will always call the local version. DUH. So it is implemented so people would be reminded

Reimplemented in MODEL::BinProbe, and MODEL::BinDwellProbe.

Referenced by write_data().

void tick ( ) [virtual]
 

called to make things work, for each one

Reimplemented from MODEL::TickTock.

Definition at line 38 of file probe.cpp.

void write_data ( void )
 

Call this one in the destructor

Definition at line 44 of file probe.cpp.


The documentation for this class was generated from the following files:
To get the sources or tarballs, please go to SourceForge or you can use the CVS repository.

More Info? Michael Peeters. Also, check our research website: www.alna.vub.ac.be

Last update: June 2002.


Looking for Open Source? Check out SourceForge Logo !