Re: GOTO controversy

Article View: comp.lang.misc

Article #4390

#4390

From: "John Meredith"
Date: Sun, 10 Mar 1996 20:19

9 lines
790 bytes

If a routine needs to perform some cleanup before returning
and there may be occasions where an early RETURN is required
(e.g. errors), then GO TO to transfer to a single clean-up-
and-return code block is neater than multiple copies of said
block.  Of course if the clean-up is complex, it would warrant
being a separate (internal?) procedure.
 
John D. Meredith

Technical Details

Message-ID: <Do2J4D.J4K@cix.compulink.co.uk>

Path: arc1-ca.pugleaf.net!cix.compulink.co.uk!usenet

References: <4grt4e$8fg@goanna.cs.rmit.EDU.AU> <4hl8mt$4po@newshost.cyberramp.net> <wallaceDnvoEo.7L7@netcom.com>

Show Full Headers

Complete Article Headers

Newsgroups: comp.lang.misc,comp.lang.c,comp.lang.pl1
Path: arc1-ca.pugleaf.net!cix.compulink.co.uk!usenet
From: jdm17@cix.compulink.co.uk ("John Meredith")
Subject: Re: GOTO controversy
Message-ID: <Do2J4D.J4K@cix.compulink.co.uk>
Organization: Compulink Information eXchange
References: <4grt4e$8fg@goanna.cs.rmit.EDU.AU> <4hl8mt$4po@newshost.cyberramp.net> <wallaceDnvoEo.7L7@netcom.com>
Date: Sun, 10 Mar 1996 20:19:25 GMT

Reply to Parent Message