Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!mintaka!bloom-beacon!eru!hagbard!sunic!dkuug!iesd!iesd.auc.dk!richard From: richard@iesd.auc.dk (Richard Flamsholt S0rensen) Newsgroups: comp.lang.c Subject: Coding Standards - enforcing rules is an overkill Keywords: return-statements, coding style, rules Message-ID: Date: 20 Nov 90 13:58:31 GMT References: <1990Nov18.034120.2963@bushido.uucp> Sender: news@iesd.auc.dk (UseNet News) Organization: Mathematics and Computer Science, University of Aalborg Lines: 22 In-reply-to: jdarcy@encore.com's message of 18 Nov 90 18:03:18 GMT In article jdarcy@encore.com (Jeff d'Arcy) writes: >dbc@bushido.uucp (Dave Caswell) writes: >>rules like having a single entrance and exit point are good >>ones. They should be written down and strictly enforced. > >Blech! Consider the following example [...] My words exactly! But, as an artist once said, describing his style: "You've got to know the rules to know when to break them". Having single exit-points is a good guideline, but it shouldn't be enforced. Same goes for using goto's, making macros containing specific variable names etc - sometimes it just *is* the best solution, also aesthetically.% Richard % no, I've never used a goto in C :^) -- /Richard Flamsholt richard@iesd.auc.dk