X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f Date: Wed, 12 Nov 2003 12:53:59 +0200 (EET) From: Esa A E Peuha Sender: peuha AT sirppi DOT helsinki DOT fi To: djgpp-workers AT delorie DOT com Subject: Re: djgpp: djgpp/src/libc/go32/makefile,overflow.S In-Reply-To: Message-ID: References: <200311070952 DOT hA79qp0D028636 AT delorie DOT com> <3FACDD1E DOT 4950D38B AT phekda DOT freeserve DOT co DOT uk> <3FAFEC80 DOT E3DF81F8 AT phekda DOT freeserve DOT co DOT uk> <3FB15BC4 DOT AF791F8 AT phekda DOT freeserve DOT co DOT uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Precedence: bulk On Wed, 12 Nov 2003, Eli Zaretskii wrote: > > Date: Tue, 11 Nov 2003 21:59:32 +0000 > > From: Richard Dawe > > > > I like the internal functions being in sections like signal, etc., because it > > shows what part of the library they belong to. > > > > OTOH putting them in internal makes it absolutely clear they are internal. > > > > I have no strong opinion either way. > > I have no strong opinions, either, but if we put them in internal, we > will need to make sure all the other internal functions are moved into > that node, for consistency. Is it worth the trouble? Maybe when we are consistent enough to document all internal functions (quite a lot of them are undocumented, for example __alloc_file, _filbuf, _flsbuf, __setup_file_rec_list, and __stdio_cleanup_proc in just ansi/stdio), but probably not right now. -- Esa Peuha student of mathematics at the University of Helsinki http://www.helsinki.fi/~peuha/