> A small LOOP with a single EXIT is relatively painless to fix. It is when > you get nested LOOPs spanning many lines with multiple EXITs (and possibly > RETURNs) in each that life becomes interesting. > > This is where evolution kicks in. The lifetime of such code is limited by > the number of people who are able and prepared to maintain it. One possible approach could be: Add the small number of “Original Oberon-2” features such as LOOP, EXIT and RETURN to the compiler just to *initially* speed up the porting effort of V4. But *eventually* eliminate those constructs *on* the then-ported system. The advantage would be that one would not need to also deal with porting complex, nested LOOP statements initially, thereby reducing risk of errors..