Re: Java needs "goto" (was Re: hi)
On 03.02.2007 13:22, Martin Gregorie wrote:
Randolf Richardson wrote:
Completely agree, Martin. "Goto" is quite nonsense - it's not needed
from a theoretical as well as from a practical point of view.
1. The ability to share code between methods within a class,
which all end with the same functionality (this could be more
efficient than calling another method; javac would need to generate
errors such as attempts to access variables that belong to different
methods, return type mismatches, etc.)
Encapsulating the code in a private method makes for more readable code
as well as eliminating code duplication.
Plus, with modern JVM's the private method is typically inlined *if* it
is a performance bottleneck. If not, it's not worth bothering about the
method invocation overhead anyway.
Side note: I am amazed that the "issue" of "goto" keeps popping up. The
high time of Basic has long since gone but people still seem to cling to
this ancient concept. Or do all these folks use assembler during their
daily work?
Regards
robert