🚀 go-pugleaf

I'm a recovering C/C++ programmer myself and am curious about this thread.
It would seem to me that the advantages of the "Single point of exit"
approach would apply as well to Java as it would to other languages.  Yet,
it seems that some people here think it really doesn't.  Is it that some of
you don't agree with this guideline at all, or do you think  that it is good
in procedural languages and not necessary in Java?

-mark

-------
Mark Meuer
Software Engineer
Life Navigator, Inc.
mmeuer@lifenavigator.com

Matt Sweetnam <msweetnam@privitygroup.com> wrote in message
news:37CEE3D5.EFC7D06B@privitygroup.com...
> I sense an ex-"C" developer :o)
>
> Tor Iver Wilhelmsen wrote:
>
> > "Dillan Fernando" <dillan@geocities.com> writes:
> >
> > > public boolean dummy()
> > > {    for(a=0;a<x;a++)
> > >     {    if (a==b) return true
> > >     }
> > > return false;
> > > }
> >
> > Procedural programmers will balk at it and mumble something about
> > "single exit point": to please them, rewrite it like this:
> >
> > public boolean dummy() {
> >   boolean retVal = false;
> >   loop: for (int a = 0; a < x; a++) {
> >     if (a == b) {
> >       retVal = true;
> >       break loop;
> >     }
> >   }
> >   return retVal;
> > }
> >
> > Note: The "loop" label here is redundant, and only there for
> > readability purposes.
> >
> > (I assume your sample code was just an illiustration: The method below
> > is a much faster version:
> >
> >  public void dummy() {
> >    return ((b >= 0) && (b < x));
> >  }
> >
> > )
>