home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!bunyip.cc.uq.oz.au!uqcspe!cs.uq.oz.au!warwick
- From: warwick@cs.uq.oz.au (Warwick Allison)
- Newsgroups: comp.lang.c++
- Subject: Re: GOTO, was: Tiny proposal for na
- Message-ID: <10115@uqcspe.cs.uq.oz.au>
- Date: 3 Sep 92 23:37:39 GMT
- References: <rmartin.715001372@thor> <4192@papaya.bbn.com> <rmartin.715447981@thor> <185270INNg9d@cs.utexas.edu>
- Sender: news@cs.uq.oz.au
- Reply-To: warwick@cs.uq.oz.au
- Lines: 32
-
- lwb@cs.utexas.edu (Lance W. Bledsoe) writes:
- >rmartin@thor.Rational.COM (Bob Martin) writes:
-
- >>Are you lazy? I doubt it. But you have decided to ignore some of the
- >>lessons of the past.
-
- >OK, I can't stand it any more. I don't know about the rest of you, but I'm
- >getting really tired of seeing "I'm the expert, listen to me" posts from
- >Bob Martin.
-
- To negate this, I have found all of Bob's posts to be spot-on. The last time
- I used a goto was in a BASIC program in 1986. I didn't even KNOW they were
- in C until I saw some code a Fortran programmer had written (well, converted).
-
- As for state machines, using GOTOs would have to be THE most kludgy way
- of doing it. Surely a MUCH more dynamic state machine could be built by
- using a few nice classes.
-
-
- I also think the "state machine" argument is a great laugh. I wouldn't mind
- betting that the proponents of that argument writing programs that are
- state machines BECAUSE they use so many gotos!!!
-
-
-
- --
- Warwick
- --
- _-_|\ warwick@cs.uq.oz.au /Disclaimer:
- / * <-- Computer Science Department, /
- \_.-._/ University of Queensland, / void (if removed)
- v Brisbane, Australia. /
-