X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
Date:	Fri, 31 Dec 2004 12:37:23 -0700
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Subject:	Re: restrict keyword
In-reply-to:	<200412311451.iBVEpBFq001103@speedy.ludd.ltu.se>
To:	djgpp-workers AT delorie DOT com
Message-id:	<d0abt01prnghfmpqc88hooanh7q6ic04mc@4ax.com>
Organization:	Systematic Software
MIME-version:	1.0
X-Mailer:	Forte Agent 1.93/32.576 English (American)
References:	<200412311451 DOT iBVEpBFq001103 AT speedy DOT ludd DOT ltu DOT se>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id iBVJbaVX006069
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

On Fri, 31 Dec 2004 15:51:11 +0100 (CET), ams AT ludd DOT ltu DOT se wrote:

>+#if __GNUC__ < 3 /* || (__GNUC__ == 3 && __GNUC_MINOR__ < 1)*/
>+#define restrict
>+#endif

We really don't want to do this as it could mess up the user's space.

I encountered this situation on a project where one module header
declared a struct member flag and another module header #defined flag
to something, so you had to be careful where you #included the latter.

I'd suggest one or more underscores _restrict or _RESTRICT_ or
__restrict__. 

-- 
Thanks. Take care, Brian Inglis

- Raw text -