Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!convex!grogers From: grogers@convex.com (Geoffrey Rogers) Newsgroups: comp.lang.c Subject: Re: C common practice. (what it really is) Message-ID: <1991Apr27.024634.586@convex.com> Date: 27 Apr 91 02:46:34 GMT References: Sender: newsadm@convex.com (news access account) Organization: Convex Computer Corporation, Richardson, Tx. Lines: 16 Nntp-Posting-Host: mozart.convex.com In article tmb@ai.mit.edu (Thomas M. Breuel) writes: >In terms of compilation speed and code optimization, having only one >function per source file is about the worst you can possibly do: you >pay the cost for parsing lots of include files for each function you >compile, and, with most compilers, you inhibit all global optimization. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Huh???? What do you mean by global optimization? Most texts on optimization consider global optimization to be between basic blocks within a procdure. Having one function per source file does not inhibit this. Everything else that you said is true/good common sense. +------------------------------------+---------------------------------+ | Geoffrey C. Rogers | "Whose brain did you get?" | | grogers@convex.com | "Abbie Normal!" | | {sun,uunet,uiucdcs}!convex!grogers | | +------------------------------------+---------------------------------+