I presume you have never had to maintain programs written in a language totally lacking structured code elements like assembler or to a lesser degree fortranIV.
I have.
Believe me:
GOTO's ( or conditional and unconditional branches, jumps or transfers ) ARE EVIL !
It's som much easier to follow a program with FOR , IF ... ELSE LOOP and CASE .
To untangle assembler programs I marked the loops and jumps with long arrows
on the printed programs - so much work just to get the overall picture
that's emediatelly apparent in structured code!
IMNSHO however we shall not abandon the GOTO before we have some exception handling mechanism - like try / catch in java. Just don't use them when the 'structured' alternative exists.
-- mats
PS. The lack of indentation i assembler and the short names (6char) and
numeric labels in fortranIV contributed to the unredability too.
Mark Johnson wrote:
I'd love to see this test. What's the hatred with the GOTO's. If they're so bad, then let's vote to remove them from the compiler. Let's remove RETURN TO and CLEAR while we're at it as well.
------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
