Xref: utzoo comp.software-eng:2652 comp.misc:7630 Path: utzoo!attcan!uunet!samsung!usc!apple!netcom!hue From: hue@netcom.UUCP (Johathan Hue) Newsgroups: comp.software-eng,comp.misc Subject: Re: Coding standards (was Re: Programmer productivity) Message-ID: <5008@netcom.UUCP> Date: 9 Dec 89 07:03:22 GMT References: <34796@regenmeister.uucp> Followup-To: comp.misc Organization: NetCom- The Bay Area's Public Access Unix System {408 997-9175 guest} Lines: 15 In article , wayne@dsndata.uucp (Wayne Schlitt) writes: > hmmm... one of the first things i usually do to code that i get off > the net is break it up into one function per file. i am not that > dogmatic about it, i just it because it seems to me to be easier to > work with. You're giving up some features of the language if you do that. You no longer have static functions, or static variables outside of functions, so everything becomes global, and good luck if someone decided to have a global and a static with the same name. You also lose some compiler optimizations. For instance, most C compilers can't do inline functions if caller and callee aren't in the same file. -Jonathan