>I don't want to get the GOTO thread started again either (lest I be forced to
>kill someone)! However, as mentioned in previous threads regarding JAVA, my
>C experience has "gone by the wayside". Having worked on another platform
>that required GOTO's for exception handling, is the following the ONLY way to
>do this in ILE C?
I don't know about ILE C. Java has throw/catch/try stuff for exception handling, same as C++, that doesn't use GOTOs explicitly.
>> By the way, I have only encountered two cases that I can recall that
>> absolutely required the use of GOTOs:
>> 1)College program where we had to simulate recursion
>> 2)CL (and any other language that does not have the minimal keywords/
>> op codes needed to write structured code)
>2) is another example for my previous question, hence my reticence in
>debunking the methodolgy outright...
Maybe you remember something called CLfree that NEWS/400 or Midrange Computing published a couple years ago. It added structured commands you could use in CL source—things like FOR, WHILE, etc. It used a REXX procedure to convert your structured code into "real" CL, with lots of labels and GOTOs, but you don't need to maintain that member, just the "structured" one.
This is just one of the reasons I prefer RPG to CL for anything that remotely gets into decision structures. I know you can do display files in CL, e.g., but for any complexity at all, it's a real pain. At one of my previous positions, we never used CL to process displays, at this one we almost always do—historical choices, etc. IMNSHO :-), using CL for displays is definitely not an example of eschewing obfuscation!
+--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: email@example.com +---
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact