X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Tue, 30 Jul 2013 16:52:59 -0400
Message-Id: <201307302052.r6UKqxww019836@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <3df2f50f-9543-47a7-8e40-a9be82ce5018@googlegroups.com> (message
	from Georg Potthast on Tue, 30 Jul 2013 13:15:37 -0700 (PDT))
Subject: Re: _CRT0_FLAG_NULLOK
References: <21e77579-1a40-4442-8111-fc976fba78fc AT googlegroups DOT com>
 <b5o37qFldl9U1 AT mid DOT dfncis DOT de> <f24e8cd3-83ca-4386-a319-a9adb4d74c68 AT googlegroups DOT com> <3df2f50f-9543-47a7-8e40-a9be82ce5018 AT googlegroups DOT com>
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> I still feel it would be a better "user experience" if atoi() would
> not crash. As far as I understand the specification does not require
> atoi() to crash if a NULL pointer is passed.

The specifications *do* require the user to pass a pointer to a string
to atoi(), though, and you did not.

It was never the intention of DJGPP to make it easy for the user to
write invalid code.