Xref: utzoo comp.software-eng:2539 comp.misc:7510 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!brutus.cs.uiuc.edu!apple!mips!prls!philabs!ttidca!hollombe From: hollombe@ttidca.TTI.COM (The Polymath) Newsgroups: comp.software-eng,comp.misc Subject: Re: Coding standards (was Re: Programmer productivity) Message-ID: <8049@ttidca.TTI.COM> Date: 29 Nov 89 02:12:00 GMT References: <34796@regenmeister.uucp> <2226@jato.Jpl.Nasa.Gov> <128179@sun.Eng.Sun.COM> <546@sagpd1.UUCP> Reply-To: hollombe@ttidcb.tti.com (The Polymath) Distribution: na Organization: The Cat Factory Lines: 31 In article <546@sagpd1.UUCP> jharkins@sagpd1.UUCP (Jim Harkins) writes: }In article dopey@sun.UUCP (Can't ya tell by the name) writes: }>I would set strict standards that deal with well written programs }>(e.g. IMHO ... one routine per file ... }I've never understood why one routine per file is such a *good* thing and }thou shalt not deviate from this under penalty of dirty looks. In a lot }of cases I feel that routines that belong together should be in the same }file. ... I think this goes back to the days of Data General FORTRAN compilers that _required_ one routine per file. I used to do a lot of work with those beasts. Keeping the common blocks straight was such a pain the company wrote an elaborate utility to automate most of it (and, incidentally, implement a pretty nifty data dictionary). This is the only environment I've ever worked in where the "one routine per file" rule was even considered. The only real advantage I can see for it is cheaper (faster) compiles because only the changed routines get re-compiled. In these days of relatively cheap CPU cycles that's a poor trade off for the hassle of keeping track of all those little files. I agree with Jim's attitude and have found it to be the de facto situation in most of the jobs I've done (and am doing). Related routines and functions should be grouped together and invisible to anything that doesn't need to use them directly. -- The Polymath (aka: Jerry Hollombe, hollombe@ttidca.tti.com) Illegitimis non Citicorp(+)TTI Carborundum 3100 Ocean Park Blvd. (213) 452-9191, x2483 Santa Monica, CA 90405 {csun|philabs|psivax}!ttidca!hollombe Brought to you by Super Global Mega Corp .com