Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!stanford.edu!eos!aio!gothamcity.jsc.nasa.gov!shirley
From: shirley@gothamcity.jsc.nasa.gov (Bill Shirley)
Newsgroups: comp.lang.c
Subject: Re: C common practice. (was: low level optimization)
Message-ID: <1991Apr26.144932.23593@aio.jsc.nasa.gov>
Date: 26 Apr 91 14:49:32 GMT
References: <21846@lanl.gov> <1991Apr19.055002.3399@Think.COM> <21964@lanl.gov> <15904@smoke.brl.mil> <22354@lanl.gov> <22524@yunexus.YorkU.CA>
Sender: news@aio.jsc.nasa.gov (USENET News System)
Organization: Software Technology Branch - NASA/JSC
Lines: 18

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. ...
|> 
|> Jim, you have no idea what you are talking about, so why talk so
|> much? Remember that a closed mouth gathers no foot. 
|> 
|> oz


Isn't the first comment basically aimed at developing procudures to be put
into a library.  Thus, if each procedure is in a different file then it also
has a different object file and when linked in from a library only those
procedures that are used need to be included in the executable.

	Bill S.