17 Nov
2006
17 Nov
'06
4:22 p.m.
On Fri, Nov 17, 2006 at 01:12:55PM +0100, Stefan Reinauer wrote:
The initial idea is that the use of goto makes it hard for the compiler to do code flow optimization.
The initial idea why you should _not_ use GOTOs is that GOTOs suck ;-) There was a paper called "Go To Statement Considered Harmful" from Edsger W. Dijkstra (and that man probably knows what he's talking about) in 1968 (!). GOTOs usually produce unreadable, unmaintainable code and should generally not be used.
But yeah, in low-level programming it may make sense in certain situations, as the code sometimes gets very ugly otherwise...
Uwe.