HP3000-L Archives

March 2004, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Patrick McMahon <[log in to unmask]>
Reply To:
Patrick McMahon <[log in to unmask]>
Date:
Fri, 12 Mar 2004 14:11:55 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Absolutely John, I have seen some horrific spaghetti with no GO TO's and I
might add that I have also seen some very fine, easy to follow, code
judiciously using the unconditional branch. Of course I've been at it for 40
years so I've seen just about everything.

> -----Original Message-----
> From: John Clogg [SMTP:[log in to unmask]]
> Sent: Friday, March 12, 2004 1:39 PM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] GO TO -- scary statistics...
>
> Tracy Pierce wrote (among other things):
> >...you can't make spaghetti code without goto.
>
> Oh yes you can!  I have seen horribly confusing code that didn't (overtly)
> use GOTOs.  I say "overtly" because as I and others have pointed out, it's
> possible to use a PERFORM command to accomplish a GOTO.  As has also been
> pointed out, the PERFORM...THRU is also an excellent tool for creating
> spaghetti code.  If GOTO-less code is written WELL, it is indeed free of
> spaghetti and other forms of confusion, but the idea that removal of GOTOs
> alone is sufficient to accomplish that is a notion with which I can't
> agree.
>
> Regards,
> John Clogg
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2