Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: C common practice.
Message-ID: <15958@smoke.brl.mil>
Date: 24 Apr 91 07:19:02 GMT
References: <21964@lanl.gov> <15904@smoke.brl.mil> <22354@lanl.gov>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 14

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.  Skilled
-C programmers recommend it - they don't avoid it or condemn it.

Gee, thanks for telling me what C gurus recommend.

-If the loaders on UNIX machines were modified to load only those
-procedures which were actually called, then I would not hesitate
-to recommend combining procedures into common files whenever
-possible.

Oh, so THAT's what you mean by "C guru" and "skilled C programmer":
yourself.  I was wondering.