Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site opus.UUCP Path: utzoo!watmath!clyde!burl!hou3c!hocda!houxm!houxz!vax135!floyd!cmcl2!seismo!hao!cires!nbires!opus!rcd From: rcd@opus.UUCP (Dick Dunn) Newsgroups: net.lang Subject: GOTOs in COBOL Message-ID: <529@opus.UUCP> Date: Tue, 5-Jun-84 21:08:14 EDT Article-I.D.: opus.529 Posted: Tue Jun 5 21:08:14 1984 Date-Received: Thu, 7-Jun-84 19:04:42 EDT References: <820@sdcsvax.UUCP>, <3431@fortune.UUCP> <127@wnuxb.UUCP> Organization: NBI, Boulder Lines: 15 >>There's no way you can avoid GOTOs in COBOL, try as you might. > >I'm not sure I believe this. I would like to be convinced that >this is so. Whether one should or should not use GOTOs in COBOL >is, of course, an entirely different matter. Actually, it's quite possible to write a fair bit of COBOL without GOTOs. I did write a few thousand lines (which in COBOL isn't all that much) without any GOTOs just because I was too lazy to figure out the interaction between GOTO and PERFORM. (And all the COBOL, BASIC, and SNOBOL fans can say what they will; mixing procedure call/return with open code is a dumb idea!) -- Dick Dunn {hao,ucbvax,allegra}!nbires!rcd (303)444-5710 x3086 ...Never offend with style when you can offend with substance.