Re: Descriptive exceptions

From:

"Alf P. Steinbach" <alfps@start.no>

Newsgroups:

comp.lang.c++.moderated

Date:

Thu, 22 Feb 2007 03:31:55 CST

Message-ID:

<544st5F1upl4cU1@mid.individual.net>

* Eugene Gershnik:

Alf P. Steinbach wrote:

* Eugene Gershnik:

1) [log as soon as possible] "if you can" - you never can
since you don't know whether the caling code wants you to log

Why shouldn't one know that? It's easy to arrange.

Possible but not easy and it heavily contradicts the KISS principle.

Some ways to do communicate level or details of logging to code that you
call:

   * The logging is done via a logger object that the calling code
     supplies at module initialization; the level of logging can be set
     dynamically via that object.

   * The called code resides in template classes that are specialized
     with a logging policy; the level of logging is set statically, but
     can be different for different specializations.

   * There is a singleton that can be configured dynamically with what
     what to log or otherwise, used via RAII objects declared in the
     calling code.

What's not easy?

In contrast, with logging in catch clauses all over the system, the
level or details of logging are hardwired in numerous places.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

      [ See http://www.gotw.ca/resources/clcm.htm for info about ]
      [ comp.lang.c++.moderated. First time posters: Do this! ]