Meeting 11: Unterschied zwischen den Versionen

Aus Java Student User Group Austria - Java + JVM in Wien Österreich / Vienna Austria
Wechseln zu: Navigation, Suche
(wSjUYxnOApcJd)
(cGPqEmPVTTvBJRK)
Zeile 1: Zeile 1:
Wow Tom,Thats a lot of anger at  Cedric's still speadring FUD'.First, still speadring  is quite a reach since his blog post is from 2005 (2 years before your bile-filled comment).Second, FUD ? Fear, uncertainy, doubt?  Reasonable doubt, based on Cedrics technical concerns does NOT constitute FUD.You need to settle down a bit and stick to discussing the technical merits of your view in the future  not berating people who don't necessarily agree with you.K
+
I'd say that this is what block scoping was ietnnved forAlthough rarely used or at least intentionally thats why you can always enclose things with {} and get a scopeFirst off it basically negates the need to set to null. Second off, this is the ultimate trick for efficiency nuts since it clues the VM/compiler to the fact that this is a nice place to do direct register assignment.  Of course I bet the first IO call you make negates all of thse tricks If you're using web services or RMI or whatever than this is the least of your worries.

Version vom 16. Dezember 2012, 07:33 Uhr

I'd say that this is what block scoping was ietnnved for. Although rarely used or at least intentionally thats why you can always enclose things with {} and get a scope. First off it basically negates the need to set to null. Second off, this is the ultimate trick for efficiency nuts since it clues the VM/compiler to the fact that this is a nice place to do direct register assignment. Of course I bet the first IO call you make negates all of thse tricks If you're using web services or RMI or whatever than this is the least of your worries.