home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!yale.edu!ira.uka.de!rz.uni-karlsruhe.de!fg30.rz.uni-karlsruhe.de!gm08
- From: gm08@fg30.rz.uni-karlsruhe.de (Steffani)
- Newsgroups: comp.lang.c
- Subject: Re: a question about if and case
- Date: 15 Dec 1992 12:44:54 GMT
- Organization: University of Karlsruhe, Germany
- Lines: 18
- Message-ID: <1gkk06INNs8o@nz12.rz.uni-karlsruhe.de>
- References: <1gi6poINN3lv@nz12.rz.uni-karlsruhe.de> <Mf=CaVW00aw4QDV2dx@andrew.cmu.edu>
- Reply-To: gm08@rz.uni-karlsruhe.de
- NNTP-Posting-Host: fg30.rz.uni-karlsruhe.de
-
- In article <Mf=CaVW00aw4QDV2dx@andrew.cmu.edu> dw3u+@andrew.cmu.edu (Daniel C. Wang) writes:
- >GM08@DKAUNI2.BITNET (hans friedrich steffani) writes:
- >>
- >> or is there a third way??
- >> i need contructions like this very often so i need a GOOD
- >> solution.
- >
- >The first way is more readable the second probably marginaly faster
- >during compile time. Can't think of a third way off hand that would
- >be worth mentioning. I'd stick with readablity over 'speed.'
- thats the problem:
- most people think that many cases with one code are bad to read.
- but i think reading many if s is not better.
- a aggree that readablity is more neccessary than speed.
-
- ---
- hans friedrich steffani
-
-