Been there, done that. Didn't use the preprocessor.
After the company began switching to Java, the client side was easily
ported. Had I been relying on the preprocessor, it would have been
difficult.
For a system like this, file / line numbers are insufficient anyway. I
implemented full stack trace, and this worked well.
The system was enabled on all productions servers all the time, with no
measurable performance impact.
But I think we are getting further and further away from the original topic.
The OP's point was that Android tools not supporting preprocessing is a
horrible disaster and enough to call Android as a whole a failure. I
think we can all agree that this is not the case.
-- Kostya
04.08.2010 10:46, Bob Kerns пишет:
There are other uses besides logging, or at least the kind of logging
you're thinking of.
For example, let's say you have a large complex server with large
complex datastructures with long lifetimes, and a high server
availability requirement.
Let's say you experience a problem in production, that you have not
been able to reproduce in testing. Or, that you can reproduce only
with such a low frequency that slowing it down significantly is
unacceptable.
So you tag a structure with where it is created and/or modified.
You may even do this preemptively, so that you CAN log and analyze
these post-failure.
There are a few other circumstances, even less common.
And don't assume that performance is not important for logging. The
more efficient logging is, the more you can afford to use it, and the
better you can maintain your program while in production.
--
Kostya Vasilev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
