"Jeff Garland" <jeff@[...].com>  writes:

| My approach was a bit different in that I didn't bother with the buffer at
| all, but created the ostream interface directly in hope that the compiler
| could obviously optimize out any calls to the stream output.  This would allow
| me to insert tracing in time sensitive code and expect that when I replace it
| will null ostream the code would be totally optimized away -- costing nothing
| in space or time.

But if you are going to compile anyway, then you could use other
methods as well (pre-processor).
 
| //The essence of the idea...
| //no char templates for simplicity of illustration
| class null_ostream : public std::ostream {
| public:
|   null_ostream() {};
> 
|   //various required overloads...
|   null_ostream& operator <<(bool) 
|   {
|     return *this;
|   }
|   null_ostream& operator <<(short) 
|   {
|     return *this;
|   }
|   //... and many more ....

How will this behave for user defined types?
Do I have to add a operator<< for both ostream and null_ostream?

-- 
	Lgb
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost