using break <label> instead of goto <label>

[MLY.G.SHADES%MIT-OZ at MIT-MC.ARPA]

	agreed that a significant amount of all software production is
spent doing simple maintenance i still agree with doug gwyn that clear
thinking (i.e. good old common sense) would improve correctness,
maintainability, and reduce cost more than compiler enforced rules.
	something that i have noticed out in the "real" world is that 
the more complex the language rules, no matter how rigidly enforced, 
the more drastic the increase in the time necessary for the 'average' 
(six month matchbook cover) programmer to produce even the simplest of
programs (unfortunately these are also the ones least likely to use
their common sense).  it cuts both ways. rigidity and higher costs in
development or looseness and higher maintenance costs.  
	one major problem that i commonly see is that the more junior
the programmer the more likely he/she/it will be doing the
maintenance. this is a serious problem.  the person with the least(!)
experience is given the job where that person can do the most damage.
(sigh)

	anyway when it gets down to brass tacks my objection to break
label is mainly on the grounds that enforcing the construct properly
would be adding a grievous burden upon the compiler.  if the label is
placed before the block that it escapes the compiler must generate two
internal labels for that label, one for the break and one for a
possible goto.  this is of course only a hazard on smaller machines
supporting small symbol tables but it still is an unecessary