Date: Tue, 2 Sep 2003 08:35:47 -0400
Message-Id: <200309021235.h82CZle7015507@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <F1A9C8D7A58D1B45A9C16FE7E3DA83D702188F@server.HME.hme.ltd.uk>
	(Melvin AT HME DOT Ltd DOT uk)
Subject: Re: Non-compliant strxfrm
References:  <F1A9C8D7A58D1B45A9C16FE7E3DA83D702188F AT server DOT HME DOT hme DOT ltd DOT uk>
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


> The only thing bothering me now is the the statement in the standard
> that says "If n is zero, dst is permitted to be a null pointer."
> Does this imply that if n isn't zero then dst must point to something?
> If so, what should we do about it?

If dst points to invalid memory there is little we can do about it.
The OS will detect any access faults automatically.  Letting it do
that is what most of the other libc functions do.