X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
In-Reply-To:	<200702212121.l1LLLP0H005802@envy.delorie.com>
Subject:	Re: Addition of some GCC headers from Linux?
To:	djgpp-workers AT delorie DOT com
X-Mailer:	Lotus Notes Release 7.0.2 September 26, 2006
Message-ID:	<OFDCE2CC01.7CDCF4D5-ON87257289.0075E438-87257289.00762618@seagate.com>
From:	Gordon DOT Schumacher AT seagate DOT com
Date:	Wed, 21 Feb 2007 14:30:30 -0700
X-MIMETrack:	Serialize by Router on SV-GW1/Seagate Internet(Release 7.0.1 HF29|March 07, 2006) at
	02/21/2007 01:30:34 PM
MIME-Version:	1.0
X-Proofpoint-FWRule:	outbound2
X-Proofpoint-Virus-Version:	vendor=fsecure engine=4.65.5502:2.3.11,1.2.37,4.0.164 definitions=2007-02-21_06:2007-02-20,2007-02-21,2007-02-21 signatures=0
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

DJ Delorie <dj AT delorie DOT com> wrote on 02/21/2007 02:21:25 PM:

# One note of warning: copying linux headers contaminates djgpp's
# copyright.  If there's a spec it's following, the headers should be
# written from the spec, not from copying.  That's how we did all the
# other headers.

Good to know on that; I'll watch out for that and do it as a rewrite.

# libc-specific headers should live in the src/libc tree somewhere if
# they're specific to a subdirectory, or in include/libc if they're
# libc-global.

What I have in mind is at least libc-global - but it could be
beneficial to "user-land" code as well to be able to use these macros.
There doesn't seem to be any officially recognized location for them
to exist, though, so I'm not sure that there would be a whole lot
of benefit to them being externally visible except for DJGPP-specific
code.

- Raw text -