[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Cron-bug] The one function thing

From: Jeff Bailey
Subject: Re: [Cron-bug] The one function thing
Date: Tue, 23 Oct 2001 05:51:00 -0700
User-agent: Mutt/1.2.5i

On Mon, Oct 22, 2001 at 11:56:55PM -0400, Ryan M. Golbeck wrote:

> Just a question about your one function per file thing.  Do you group
> related functions into one header then?  Like, say we have a couple of
> alloc, free and such functions for a job entry structure.  You would
> have their prototypes in one header, say entry.h, even though their
> functions are spread out through different files?

This is something that's bothered me for a bit, because I want to
group prototypes into appopriate headers, but I tend to wind up with
seperate .h files for each one anyway.  (It helps keep my confusion
down).  I'm not picky here, because prototypes don't need to be
modified as much as actual source code.

I also wind up with a couple additional headers for any #define's that
I wind up using.  I wonder if a good solution is one header per
prototype and then a few headers that define chunks of them at once.

Abandon the search for truth; settle for a good fantasy.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]