----- Original Message -----
From: "Dave Cramer" <Dave@micro-automation.net>
Sent: Saturday, March 16, 2002 4:15 PM
> Do we want to put logging in the driver?
> Why?
> How much?
> At what cost?
Needless to say, logging is essential thing to have,
but to answer the above questions one answer could be - to try.
If those who care about the logging facilities, could
simply mirror current dev. tree of the driver, and some in,
and compare performance between the two on the same set of
tests.
Another possible solution just came into my not-always-so-smart-head,
is to write some pre-processing ourselves :). Put some special types
of comments in the places where the logging seems appropriate like:
//{DEBUG
logSmthHere();
//}DEBUG
Just a simple {PERL, Shell, Python, whatever}-script may run through the sources
and produce two jars, one compiled with DEBUG as it is, the other
one will be a stripped out //{DEBUG version. Yes, I know this will require
some tmp space and some extra processing, but could be a solution too.
2 Canadian cents
-s