Re: [boost] [log] Comments

Subject: Re: [boost] [log] Comments
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-03-15 14:32:53

Andrey Semashev wrote:
> On 03/15/2010 01:45 PM, Vladimir Prus wrote:
>
> > * Why is trivial logging printing the sequental number of
> > each log message?  I don't think this helps anything.
>
> Record identifiers proved to be very useful in communication,
> surrounding the piece of log. It's much easier to write "see, there's
> that error in line 2764" than to go for lengthy explanations
> of how to find it in the file.

Since there's no binary logging, the output is likely to be written to a file.  I can use many means to determine a line number from the contents of a text file without embedding a line number proxy.

> > Finally, I think by default, everybody things of logging as
> > glorified std::cout, so trivial logging better print messages
> > to console, not to a file.
>
> I disagree. First, you don't need the library to spam the console.

Who are you to say what we need WRT the console?  We frequently write output to stderr with the express intention of redirecting it to a file or pipeline.

> Second, I consider spamming the console to be a bad idea in the first
> place. In my practice there are cases when writing _anything_ on the
> console is forbidden.

That doesn't mean doing so is wrong for anyone else.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.