Xref: utzoo comp.lang.c:14840 comp.std.c:579
Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c,comp.std.c
Subject: Re: Definition of isprint()
Message-ID: <9206@smoke.BRL.MIL>
Date: 16 Dec 88 21:04:49 GMT
References: <474@sdrc.UUCP> <9182@smoke.BRL.MIL> <1988Dec15.181144.2066@utzoo.uucp>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <1988Dec15.181144.2066@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>Alas, the wording at the head of section 4.3 (October draft) just says
>"implementation-defined" without narrowing it down further.  A footnote
>[note that footnotes are not binding on implementors, as they are not
>officially part of the standard] pins down what this means for ASCII,
>but not more generally.

Yes, I checked this with our fearless Redactor, who assures me that
the Committee deliberately decided not to be more specific about
these functions even in the "C" locale.  Given the wide variety of
display technologies in use, it's not clear that many of these
functions are all that useful anyway.  (isspace() is about the best.)