DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16229>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16229

Convenience methods to cut object allocations in application code

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Convenience methods to cut  |Convenience methods to cut
                   |execution speed in          |object allocations in
                   |application code            |application code



------- Additional Comments From [EMAIL PROTECTED]  2003-01-18 21:33 -------
Hello Matt!

I don't see the point of your checkedDebug() method. It does exactly the same 
thing as the debug()-method except that same tests are run twice (if enabled).

Your suggestion is that I create a concatenation object instead of creating the 
StringBuffer. If I take some liberty with your suggestion this will look like 
this in my application (example from Jake):

logger.debug(new Concatenator("some string", somevar,
                              "another string", anothervar));

I considered this solution but I have two things against it. Firstly, this 
means that somewhere in my code I will have this utility class or more likely 
it will be implemented differently in several different parts of my code by 
different developers and some will forget about it. Secondly, this suggestion 
results in the creation of the Concatenator object wether debugging is on or 
off. It is better than the creation of StringBuffer+String but not good enough.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to