X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Fri, 24 Dec 2004 14:19:49 -0500
Message-Id: <200412241919.iBOJJnq5014101@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <Ub6dnQHCSdfA-lHcRVn-1w@comcast.com> (message from Joe Wright on
	Fri, 24 Dec 2004 14:00:53 -0500)
Subject: Re: CTYPE stuff for Eli or DJ
References: <KpSdnePxHo9G_VHcRVn-oQ AT comcast DOT com> <200412241848 DOT iBOImiRM013524 AT envy DOT delorie DOT com> <Ub6dnQHCSdfA-lHcRVn-1w AT comcast 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


> Even faulty, if '(int)(c)+1' is not in range do we risk segfault or 
> other awful outcome? Kaz' demons come to mind.

Most libc functions will segfault if you pass them faulty data.  It is
up to the application to ensure robust usage of libc functions.

Frankly, I'd rather see your application segfault than silently do the
wrong thing.  That will encourage you to fix it ;-)