intercepting output to cout

[Marc Schellens]

I want to create an object,
which replaces std::cout
all output will be put out to std::cout, but optional
also copied to a file.

But the file output needs to be manipulated:
every new line has to be preceded by a ';'

Is there an easy way to do so?
Or do I have to write wrappers for all kind of
<< operators?

And which functions to overload to scan for '\n'
likje ostr.put(...), any other (ie. are operator<<
using put(...) (always)?)

thanks,
marc

[Ivan Vecerina]

"Marc Schellens" <m_*********@hotmail.com> wrote in message
news:ck***********@news.riken.go.jp...

I want to create an object,
which replaces std::cout
all output will be put out to std::cout, but optional
also copied to a file.

But the file output needs to be manipulated:
every new line has to be preceded by a ';'

Is there an easy way to do so?
Or do I have to write wrappers for all kind of
<< operators?

And which functions to overload to scan for '\n'
likje ostr.put(...), any other (ie. are operator<<
using put(...) (always)?)

Look for "redirect cout" ...
What you need to do is replace the streambuf associated
with std::cout:

int main(void)
{
std:ostream * saveStream = cout.rdbuf();
MyStreamBuffer newBuf(.......);
cout.rdbuf(&newBuf);
try {
... the resto of te program ...

} catch(...) { error reporting... }
cout.rdbuf(saveStream); // restore cout to original state
}

To have output to both the console and a file, you should be
able to find a 'tee' stream buffer (I do not know a specific
implementation, but there are a few floating around on the web):
http://www.google.com/search?&q=Tee%20streambuf
hth -Ivan
--
http://ivan.vecerina.com/contact/?subject=NG_POST <- e-mail contact form
Brainbench MVP for C++ <> http://www.brainbench.com

[Marc Schellens]

Ivan Vecerina wrote:

Look for "redirect cout" ...
What you need to do is replace the streambuf associated
with std::cout:

that was exactly what I needed. Thanks,
marc

[Howard]

"Ivan Vecerina" <pl*****************@ivan.vecerina.com> wrote in message
news:ck**********@newshispeed.ch...

"Marc Schellens" <m_*********@hotmail.com> wrote in message
news:ck***********@news.riken.go.jp...
int main(void)
{
std:ostream * saveStream = cout.rdbuf();
MyStreamBuffer newBuf(.......);
cout.rdbuf(&newBuf);
try {
... the resto of te program ...

} catch(...) { error reporting... }
cout.rdbuf(saveStream); // restore cout to original state
}

What if there is no exception? How does cout get restored in that case?
I'd think you'd want to use a constructor/destructor pair for the rdbuf
calls, wouldn't you? (think "RAII")

-Howard

[Ivan Vecerina]

"Howard" <al*****@hotmail.com> wrote in message
news:lB*********************@bgtnsc04-news.ops.worldnet.att.net...

"Ivan Vecerina" <pl*****************@ivan.vecerina.com> wrote in message
news:ck**********@newshispeed.ch...

"Marc Schellens" <m_*********@hotmail.com> wrote in message
news:ck***********@news.riken.go.jp...
int main(void)
{
std:ostream * saveStream = cout.rdbuf();
MyStreamBuffer newBuf(.......);
cout.rdbuf(&newBuf);
try {
... the resto of te program ...

} catch(...) { error reporting... }
cout.rdbuf(saveStream); // restore cout to original state
}

What if there is no exception? How does cout get restored in that case?
I'd think you'd want to use a constructor/destructor pair for the rdbuf
calls, wouldn't you? (think "RAII")

I would definitely use RAII -- except I wanted this post to be concise
and there is no RAII class performing the above in the standard library.
This said:
- int main() above does catch(...) { /*code*/ } to always restore the buf
- anyway it is not a good idea to let exceptions propagate out of main()

Cheers -Ivan
--
http://ivan.vecerina.com/contact/?subject=NG_POST <- e-mail contact form
Brainbench MVP for C++ <> http://www.brainbench.com

[Howard]

"Ivan Vecerina" <pl*****************@ivan.vecerina.com> wrote in message
news:ck**********@newshispeed.ch...

"Howard" <al*****@hotmail.com> wrote in message
news:lB*********************@bgtnsc04-news.ops.worldnet.att.net...

"Ivan Vecerina" <pl*****************@ivan.vecerina.com> wrote in message
news:ck**********@newshispeed.ch...

> "Marc Schellens" <m_*********@hotmail.com> wrote in message
> news:ck***********@news.riken.go.jp...
> int main(void)
> {
> std:ostream * saveStream = cout.rdbuf();
> MyStreamBuffer newBuf(.......);
> cout.rdbuf(&newBuf);
> try {
> ... the resto of te program ...
>
> } catch(...) { error reporting... }
> cout.rdbuf(saveStream); // restore cout to original state
> }
>

What if there is no exception? How does cout get restored in that case?
I'd think you'd want to use a constructor/destructor pair for the rdbuf
calls, wouldn't you? (think "RAII")

I would definitely use RAII -- except I wanted this post to be concise
and there is no RAII class performing the above in the standard library.
This said:
- int main() above does catch(...) { /*code*/ } to always restore the buf
- anyway it is not a good idea to let exceptions propagate out of main()

I misread your code. The way you put "{ error reporting... }" on the same
line as catch, I mistook that for a comment. (My old Pascal days coming
back!) And so I then mistook the buffer restore call as being inside the
catch clause. My bad!

But that's one reason I always go down to the next line before starting the
"dependant clause" after a try/catch/if/else, etc. Arranging it like this
always confuses my little mind. :-)

-Howard