deriving from ostream - Logger

[Christopher Pisz]

I set out to make a custom logger. Examining some other code laying around,
I came across one that derived from ostream, and had a associated class
derived from streambuf. Is this practice a good idea? I was under the
impression that deriving from std classes that do not have virtual methods
was bad. Is ostream designed to be derived from?

If, so are there any resources on how to do this properly? ostream has alot
if internals that look pretty difficult to..for loss of words...understand
completely.

Thanks.

[James Kanze]

On Nov 30, 5:16 am, "Christopher Pisz" <[e-mail]:

I set out to make a custom logger. Examining some other code
laying around, I came across one that derived from ostream,
and had a associated class derived from streambuf. Is this
practice a good idea?

It depends on how you implement the framework. In my case, the
"logger" is the return value of a function, which means that it
must support copy, and so deriving from ostream is out. Other
architectures are certainly possible, however, and if copy isn't
necessary, deriving from ostream is probably a good solution.

I was under the impression that deriving from std classes that
do not have virtual methods was bad.

So how does that affect ostream. Ostream has a virtual
destructor.

Is ostream designed to be derived from?

Definitly. What do you think ofstream and ostringstream do?

If, so are there any resources on how to do this properly?
ostream has alot if internals that look pretty difficult
to..for loss of words...understand completely.

For the most part, you derive from ostream for convenience: to
automatically create and destroy the desired type of streambuf.
It's also usual to provide rdbuf(), to return a pointer to the
derived type of streambuf.

In the case of a logger based on a temporary, it might make
sense to add some special "end of log record" handling in the
destructor. Plus some special function which returns a
non-const reference, to kick things off (and allow the use of
non-member << operators). Something like:

#define LOG( level ) \
ologstream( level ).start( __FILE__, __LINE__ )

for example: the constructor of ologstream connects to a
streambuf according to the level, the start function outputs the
filename and linenumber, and returns an ostream& so that all <<
operators can be used, and the destructor calls a special
function on the streambuf which flushes (but also ensures that
the output is correctly terminated with a '\n', etc.).

--
James Kanze (GABI Software) email:ja*********@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]