Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E1FEA5B.6D7B9FD8@phekda.freeserve.co.uk>
Date: Sat, 11 Jan 2003 09:56:43 +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: strlcat, strlcpy, revision 2 [PATCH]
References: <200301102322 DOT h0ANMfu27001 AT brother DOT ludd DOT luth DOT se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Martin Str|mberg wrote:
> 
> According to Eli Zaretskii:
> > > From: "Richard Dawe" <rich AT phekda DOT freeserve DOT co DOT uk>
> > > + If @var{dest} and @var{src} are overlapping buffers, the behavior
> > > + is undefined.
> >
> > What does this mean, exactly?  The specific implementation we have is
> > deterministic, right?  So it is possible to tell exactly what does it
> 
> Probably. I think he's talkning about C standard undefined behaviour.

Yes.
 
> > do when the buffers overlap, right?  If so, I think we should describe
> > the actual behavior of our implementation.
> 
> That's a good idea. But might not say much ("if they do, your code
> might do anything; at least one of the effects being writing over
> memory way out of bounds").

I'm not so sure that's a good idea. See my other mail.

Thanks, bye, Rich =]

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