Yes u r right Most compilers will inline these method calls. So it means the same thing again.I don't think we would be gaining anywhere with method calls.
-----Original Message----- From: Jesse Alexander (KXT) [mailto:[EMAIL PROTECTED] Sent: Thursday, August 05, 2004 3:56 PM To: 'Struts Users Mailing List' Subject: RE: System.out.println I think the actual compilers will optimize the method call resulting in an overhead which is not anymore measurable. I imagine they will inline the debug-method with the if and just call out for the actual println... Alexander -----Original Message----- From: Xavier Noria [mailto:[EMAIL PROTECTED] Sent: Thursday, August 05, 2004 11:37 AM To: Struts Users Mailing List Subject: Re: System.out.println On Aug 5, 2004, at 11:22, Aditya Athalye wrote: > I agree with u that those many if statements will clutter code. But a > method call everytime is also expensive in terms of performance. So it > is really a trade off between performance and Is the difference in performance really significative in a web application? Without a benchmark, I would say that in a typical response there are *lots* of method calls from the ones in your code passing through Struts/Hibernate/etc. down to the Java library. Some of them non-trivial as the ones regarding persistence. If the comparison was going to be 1 versus 1.00000000000001 (if it is measurable at all) I wouldn't see a real trade-off there. -- fxn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
