C common practice. (what it really is)

[Geoffrey Rogers]

In article <TMB.91Apr26145719 at volterra.ai.mit.edu> tmb at 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 at convex.com                 | "Abbie Normal!"                 |
| {sun,uunet,uiucdcs}!convex!grogers |                                 |
+------------------------------------+---------------------------------+