Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!decuac!shlump.nac.dec.com!tkou02.enet.dec.com!diamond From: diamond@tkou02.enet.dec.com (diamond@tkovoa) Newsgroups: comp.std.c Subject: Re: Proposed Enhancement to select/case (yes, I know...) Message-ID: <1941@tkou02.enet.dec.com> Date: 31 Aug 90 08:04:11 GMT References: <1990Aug30.164610.3519@zoo.toronto.edu> <13714@smoke.BRL.MIL> Reply-To: diamond@tkou02.enet.dec.com (diamond@tkovoa) Organization: Digital Equipment Corporation Japan , Tokyo Lines: 19 In article <13714@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes: >In article <1990Aug30.164610.3519@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes: >>In article burley@world.std.com (James C Burley) writes: >>>... how about this: allow ranges (and, perhaps, lists) on case statements. >>Such a feature appeared in one draft of ANSI C, and disappeared in the >the reason it appeared was that the preceding X3J11 meeting was held in >Europe and was overrun with Pascal freaks. The Pascalisms were removed >at the next meeting, where C freaks dominated. The Pascalisms were not removed. Prototypes, pointers to array types, and the requirement to diagnose violations of syntax and constraints made it into the final edition. There are probably others too. -- Norman Diamond, Nihon DEC diamond@tkou02.enet.dec.com We steer like a sports car: I use opinions; the company uses the rack.