Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!mintaka!ai-lab!life!tmb
From: tmb@ai.mit.edu (Thomas M. Breuel)
Newsgroups: comp.lang.c
Subject: Re: C common practice. (what it really is)
Message-ID: <TMB.91May12031907@volterra.ai.mit.edu>
Date: 12 May 91 07:19:07 GMT
References: <TMB.91Apr26145719@volterra.ai.mit.edu> <240@sojurn.UUCP>
Sender: news@ai.mit.edu
Organization: MIT Artificial Intelligence Lab
Lines: 14
In-reply-to: mike@sojurn.UUCP's message of 12 May 91 11:00:47 GMT

In article <240@sojurn.UUCP> mike@sojurn.UUCP (Mike Sangrey) quotes:

   In article <TMB.91Apr26145719@volterra.ai.mit.edu> tmb@ai.mit.edu (Thomas M. Breuel) 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.  Skilled
   >   C programmers recommend it - they don't avoid it or condemn it.

   I dare say that just because it's a function doesn't mean it should be
   in a separate file.

Please be more careful when you quote. The text you quoted had
nothing do to with me, yet in your posting, it has my name associated
with it...