From owner-freebsd-bugs Mon Jul 14 17:05:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23260 for bugs-outgoing; Mon, 14 Jul 1997 17:05:56 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA23253; Mon, 14 Jul 1997 17:05:52 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id UAA08383; Mon, 14 Jul 1997 20:05:51 -0400 (EDT) Date: Mon, 14 Jul 1997 20:05:51 -0400 (EDT) From: Garrett Wollman Message-Id: <199707150005.UAA08383@khavrinen.lcs.mit.edu> To: "Jonathan M. Bresler" Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), freebsd-bugs@FreeBSD.ORG Subject: Re: ispunct(3) [was: FreeBSD-2.1.1] In-Reply-To: <199707142331.QAA21580@hub.freebsd.org> References: <199707141916.PAA07598@khavrinen.lcs.mit.edu> <199707142331.QAA21580@hub.freebsd.org> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > Garrett, > even FreeBSD current does not seem to have UCHAR_MIN. > what system is your test program supposed to be for? Sorry... serves me right for modifying my example after having compiled it. UCHAR_MIN doesn't exist because the only permissible minimum value for any unsigned type is zero. My original program iterated over [CHAR_MIN,UCHAR_MAX], but I realized that that was incorrect and changed it in my message without re-testing. In any event, that particular error does not change the fact that Standard C requires the ctype(3) routines work for all possible values of an unsigned char, and EOF, and the old isascii() kluge should not be carried over into new code. (If you are concerned about portability to old, broken systems, include a working ctype(3)...) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick