C common practice. (was: low level optimization)

[pefv700 at perv.pe.utexas.edu]

In article <22524 at yunexus.YorkU.CA>, oz at yunexus.yorku.ca (Ozan Yigit) writes...
>In article <22354 at lanl.gov> jlg at cochiti.lanl.gov (Jim Giles) writes:
> 
>>On the contrary.  Putting each C procedure into a separate file _is_
>>common practice.  It is promoted as "good" style by C gurus. ...

I have also read or heard this, but don't remember where.  I think I 
remember jlg stating that it was common in FORTRAN to do this (although I
may be wrong).  To be honest, I had never even heard of splitting source
code for an executable into multiple files and certainly didn't know that
it was allowed in FORTRAN.

> 
>Jim, you have no idea what you are talking about, so why talk so
>much? Remember that a closed mouth gathers no foot. 
> 
>oz

Wow, where does everyone get off telling him to shut up.  If you don't
respond, he'll quit posting.