problems/risks due to programming language, stories requested

[Lou Steinberg]

In article <2596 at gmu90x.gmu.edu> jbaker at gmu90x.gmu.edu (jbaker) writes:

> In article <8218 at hubcap.clemson.edu> Bill Wolf writes:
> >From dave at micropen (David F. Carlson):
> >> A multi-case switch is very handy in many situations to reduce identical
> >> treatments for similar cases.  
> 
> But the real usefulness of requiring break in a switch statement is for
> SIMILAR treatments of similar cases, for example you may require a
> few assignments in one case before a more complicated computation which
> must be performed for several of the cases.

ARGHHH!!  That is what subroutines (and macros) are for - to handle
common code.  And if your language makes them too expensive, either in
terms of run time or in terms of programmer effort, then THAT is an
even worse problem with the language than the problems with break.
-- 
					Lou Steinberg

uucp:   {pretty much any major site}!rutgers!aramis.rutgers.edu!lou 
arpa:   lou at cs.rutgers.edu