Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E3E9D31.BE983B2A@phekda.freeserve.co.uk>
Date: Mon, 03 Feb 2003 16:47:45 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: restrict
References: <200302030730 DOT IAA16240 AT lws256 DOT lu DOT erisoft DOT se> <3E3E5F74 DOT D414BB21 AT phekda DOT freeserve DOT co DOT uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Richard Dawe wrote:
>
> Martin Stromberg wrote:
[snip]
> > However, meanwhile I've wondering if having a libc compiled with
> > restrict and using headers without restrict or vice versa can be
> > problem?
> [snip]
> 
> Scenario that I think you are thinking of: library compiled with gcc 3.x;
> program using library compiled with gcc 2.95.x.
[snip]

I should have been clearer here. gcc 3.x defaults to C89 mode at the moment,
so it won't support restrict by default. The problematic scenario would be
library built by gcc 3.x in C99 mode and the program built with gcc < 3 or gcc
3.x in C89 mode.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]