Where should the type information be 213
in the early 70s, i wrote a pli program that analysed (360) buttembler listings ... creating abstract representation of instructions and...
This is a misreading (or misrepresentation) of Rubin's work. What he showed (in, for example, his 1987 letter to CACM) is that there are *some* situations where goto appears to be the most concise and direct control structure available in typical structured procedural languages.
The 1987 example involved branching out of two nested for-loops. This situation is widely recognized and the use of goto there is relatively uncontroversial; in C terms, the goto serves as a "labelled continue", and C users acknowledge that the language does not provide syntactic sugar for that purpose (or the similar "labelled break"). In this and a few other cases (such as branching out of nested control structures on an error to a single point of return) many structured-programming advocates feel goto is a suitable choice in languages that don't provide alternative syntax (or, in some cases, an alternative built-in feature, such as exceptions for the error-handling case).
On Mon, 04 Apr 2005 02:31:46 GMT, Brian Inglis Argumentum de verecundiam doesn't work here. I recall whan this fashion arose and there were an abundance of hucksters selling...
Rubin is most certainly NOT claiming that gotos are always less confusing than other control structures. He's claiming that rejecting goto as an option a priori is a mistake (and I agree, incidentally).
--
Thanatos, thanatos! The labourer, dropping his lever, Hides a black letter close to his heart and goes, Thanatos, thanatos, home for the day and for ever. -- George Barker
Where should the type information be 214
Alt Folklore Computers from Newsgroups