Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.compilers    |    Compiler construction, theory, etc. (Mod    |    2,753 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,983 of 2,753    |
|    noitalmost to All    |
|    are there implementation reasons for not    |
|    13 Jan 11 13:09:29    |
      From: noitalmost@cox.net              I've noticed that Wirth has continually rejected the idea of a break       statement and I was wonder why. Is this purely philosophical, or are       there code optimization reasons? Naive code for a break is trivial to       implement.              Is it easier to optimize loops with no break? That is, is the cost of       having extra booleans to control the loop less than the cost of       messing up the basic blocks with break?       [It's a little easy to optimize single-exit loops, but my impression is       that the motivation was more like salvation through suffering. -John]              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca