delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-workers-bounces using -f |
Date: | 08 Jan 2004 11:30:20 +0200 |
Message-Id: | <uu13623f7.fsf@elta.co.il> |
From: | Eli Zaretskii <eliz AT elta DOT co DOT il> |
To: | Esa A E Peuha <peuha AT cc DOT helsinki DOT fi> |
CC: | djgpp-workers AT delorie DOT com |
In-reply-to: | <Pine.OSF.4.58.0401071356580.26260@sirppi.helsinki.fi> (message |
from Esa A E Peuha on Wed, 7 Jan 2004 14:18:35 +0200 (EET)) | |
Subject: | Re: stdbool.h and complex.h |
References: | <Pine DOT OSF DOT 4 DOT 58 DOT 0401071356580 DOT 26260 AT sirppi DOT helsinki DOT fi> |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> Date: Wed, 7 Jan 2004 14:18:35 +0200 (EET) > From: Esa A E Peuha <peuha AT cc DOT helsinki DOT fi> > > Can I commit complex.h now and the functions later as I write them, > or should I wait until I have all of them and then commit at the > same time? IMHO, it's better to at least have the unimplemented functions' prototypes ifdef'ed away on the header. This assumes that a non-trivial amount of functions can be implemented quickly and committed together with the initial version of the header; otherwise, I'd suggest to wait with committing the header until we have a substantial body of its functions in the library.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |