*when* it's necessary. In the example/article D uses lazy or partial evaluation to sort of get around this. In other languages there are other mechanisms. In Java perhaps there's a way of refactoring the logging such that Strings are re-used (use static final String and build logging from them?)
I'm favorable to refactoring the logging a bit to avoid unnecessary method calls and string concatenation, etc... but it's not a bit of String concatenation that makes VM run out of memory. Garbage collection does work, and gets rid of these string, before running out of memory (as per JVM spec). If there are memory leaks, lets find and address them, rather than kludging the code IMHO. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
