Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!ut-emx!perv.pe.utexas.edu!pefv700
From: pefv700@perv.pe.utexas.edu
Newsgroups: comp.lang.c
Subject: Re: C common practice. (was: low level optimization)
Message-ID: <47873@ut-emx.uucp>
Date: 25 Apr 91 13:38:05 GMT
Sender: news@ut-emx.uucp
Organization: Dept. of Petroleum Engineering, The University of Texas at Aust
Lines: 20

In article <22524@yunexus.YorkU.CA>, oz@yunexus.yorku.ca (Ozan Yigit) writes...
>In article <22354@lanl.gov> jlg@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.