harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Zakharov" <alexei.zakha...@gmail.com>
Subject Re: [classlib] logging from within our implementation
Date Thu, 01 Jun 2006 16:38:00 GMT
I worry about the situation when we got something Velocity-like in
java code. Strings like "#foreach" or smth. like it in comments. This
will probably break the V. compiler.

2006/6/1, Soeren Strassfeld <nc-straszso@netcologne.de>:
> Hi Alexei,
>
> I think the result in both examples is quite the same, I just liked
> the Idea to just add java comments to the code, so you donĀ“t
> need a precompiler as long as you build the classlib with logging
> statements.
>
> Cheers,
>  Soeren
>
> Alexei Zakharov schrieb:
> > Hi Soeren,
> >
> > 2006/6/1, Soeren Strassfeld <nc-straszso@netcologne.de>:
> >> How about using Velocity as Preprocessor.
> >> You could put all logging Statements between an
> >> //#if ($debug)
> >> and
> >> //#end
> >> So the Code would stay pure java, and the debug Version could be
> >> compiled
> >> without a Preprocessor.
> >
> > Is this something better than just using java in the same way?
> >
> > static final boolean DEBUG = false;
> > if (DEBUG) {
> >    // wiped away by java compiler
> >    log("my useful log message");
> > }
> >
> > The problem of your approach as well as the above example is the
> > additional syntax you need to add to each log call.
> >
> > However, I like the general idea of using Velocity as a Java preprocessor
> > :)
> >


-- 
Alexei Zakharov,
Intel Middleware Product Division

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message