Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!harris.cis.ksu.edu!mac
From: mac@harris.cis.ksu.edu (Myron A. Calhoun)
Newsgroups: comp.lang.pascal
Subject: Re: Gotos are ok (Was Re: IMPLEMENT GOTO ACROSS MODULES IN TURBO PASCAL??)
Summary: EXIt == (simple) GOTO
Message-ID: <1991Jan18.151104.13742@maverick.ksu.ksu.edu>
Date: 18 Jan 91 15:11:04 GMT
Expires: 1 February 1991
References: <1991Jan16.005523.28337@syacus.acus.oz> <7612@plains.NoDak.edu> <2802@oucsace.cs.OHIOU.EDU>
Sender: news@maverick.ksu.ksu.edu (The News Guru)
Distribution: usa
Organization: Kansas State University, Dept. of Computing and Information Sciences
Lines: 28

In article <2802@oucsace.cs.OHIOU.EDU> tswingle@oucsace.cs.OHIOU.EDU (Tom Swingle) writes:

   [many lines deleted]

>....(by the way isn't exit just a special form of goto?) 

Yes.  Also BREAK.  In assembly language the "GOTO-less" style was
achieved by simple renaming:  JuMP, BRAnch, etc.!-)

And CASE, THEN/ELSE/ELSEIF, and similar constructs have GOTO's
"hidden" within them.

Sometimes such "hiding" makes things easier to understand, and
sometimes working around such hiding makes things harder to understand.

Or, putting it another way,
sometimes unhidden GOTO's make things harder to understand, and
sometimes including them deliberately makes things easier to understand.

GOTO's are a tool much as a sharp knife is a tool.  They may both be
used wisely or foolishly or not at all.
--Myron.
--
# Myron A. Calhoun, Ph.D. E.E.; Associate Professor   (913) 539-4448 home
# INTERNET: mac@cis.ksu.edu   (129.130.10.2)                532-6350 work
# UUCP: ...{rutgers, texbell}!ksuvax1!harry!mac             532-7353 fax
# AT&T Mail:  attmail!ksuvax1!mac                   W0PBV @ K0VAY.KS.USA.NA