Would you rather have that 5ns, or the ace-in-the-hole where you can debug your app in an installed production environment by turning on (assuming you don't use the final static boolean method) the appropriate logger? This has been extremely helpful in debugging. It also catches lots of things you wouldn't ordinarily see, like when you add this to an ActionListener more then once and you see your actionPerformed() get called more then once. It's also useful for profiling.
I think my original email should make it abundantly clear on which side _I_ fall on this issue. :-)
In fact, I've been known to (gasp! horror!) deploy applications into production with "-g" enabled in order to be able to actually turn on with java debugging enabled and remote debug the application (on an unactive node, of course) in the production environment. I've heard of people who just start their app servers with JDWP enabled all the time for this reason, but I've never actually met one. :-)
In short, I've found that trying to save micro-amounts of time here and there in an application at the expense of debuggability and maintainability usually end up with a bad application that's also slow. Java enterprise/web applications are so seldom, in my experience, performance limited by the actual Java bytecode execution speed, as to make optimizing for that virtually irrelevant. There are so many other places to start optimizing rather than worrying about 5ns here and 5ns there, particularly before you go into production and know that you aren't suitably performant.
Kirk Wylie M7 Corporation
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
