Loop iterator - example.txt

[Walter Bright]

kris wrote:
> Alternate design strategies aside, I was always told that goto, in 
> general, lead to *less* efficient code. Didn't compilers (perhaps in the 
> past) disable the optimizer for functions with one or more instances of 
> goto? Doesn't it mess with flow analysis, or something?

I don't think any compiler built since 1982 had such limitations. In 
fact, the way the DM optimizer works is by converting all constructs to 
goto's and *then* operating on it. The algorithms to do this are well 
known, and are even in the Dragon Book (vintage 1979). Goto's will not 
adversely affect optimization at all.