Hi,
Personally, I reckon that it's the character of the coder that defines the readability of their code, not the inherent abilities of the language. Also, anyone who uses a goto in their code will always write spaghetti (:
It most definately is the character and inclinition of the writer that determines the readability of the code.
I agree. Some languages make it easier than others, though.
Carefully written, gotos can make the code shorter, more succinct, and more readable.
For example, hard-coding a finite state machine is best done with gotos. In fact, it is rather difficult to do efficiently without gotos (I've done it, but man was it *ugly*).
I learnt programming on Commodore 64 basic (written by MS, incidentally). No loops, except a primitive FOR. The IF only had a THEN (there was no ELSE). It had no real functions to speak of. Man, did I write some spaghetti code in those days.
Cheers, Carl.
