debug information

[Martijn van Rheenen]

Sounds like a good way to route the debug information to some other place
indeed. Although just reverting the std::cerr information to your own stream
could be a possibility too?

Something along the line of:
std::ofstream out(...);
std::streambuf orig = std::cerr.rdbuf(out.rdbuf());
... // use redirected cerr
std::cerr.rdbuf(orig);

as exampled in this sourcecode:
http://groups.google.com/group/alt.sources/msg/bb4204134e9956a0?pli=1

Greets,
  Martijn van Rheenen



On Wed, Apr 20, 2011 at 1:02 PM, Ivar Eskerud Smith <
ivar_eskerud at hotmail.com> wrote:

>  I have adressed this issue before, but with little response so thought I`d
> give it another try...
> I think the debug information in taglib should be made available, and not
> just sent to std::cerr. This information could be very useful. It should be
> the program that uses taglib that should decide where to show/send this
> information. A singleton class used in the "debug" function to log this
> information could be an option.
>
> Comments?
>
> regards, Ivar
>
> _______________________________________________
> taglib-devel mailing list
> taglib-devel at kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/taglib-devel/attachments/20110420/6e4de612/attachment.htm