X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Message-ID:	<428DEE0A.8A72F76F@yahoo.com>
From:	CBFalconer <cbfalconer AT yahoo DOT com>
Organization:	Ched Research http://cbfalconer.home.att.net
X-Mailer:	Mozilla 4.75 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: ctype<char> custom table lookup in C++
References:	<1116546092 DOT 867392 DOT 97940 AT g43g2000cwa DOT googlegroups DOT com> <3f5juoF5og3rU2 AT news DOT dfncis DOT de>
Lines:	29
Date:	Fri, 20 May 2005 14:22:46 GMT
NNTP-Posting-Host:	12.76.139.52
X-Complaints-To:	abuse AT worldnet DOT att DOT net
X-Trace:	bgtnsc04-news.ops.worldnet.att.net 1116598966 12.76.139.52 (Fri, 20 May 2005 14:22:46 GMT)
NNTP-Posting-Date:	Fri, 20 May 2005 14:22:46 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hans-Bernhard Broeker wrote:
> Carey Evans <carey DOT evans AT gmail DOT com> wrote:
> 
... snip ...
> 
> I find it hard to believe the C++ would actually predefine the
> implemention of a given feature.  That's none of their business.
> 
>> but with GCC 3.4.3 in DJGPP, it returns (from ctype_inline.h):
> 
>>> _M_table[static_cast<unsigned char>(__c + 1)] & __m;
> 
>> which means that all the character classifications in my custom
>> class are off by one.
> 
> Only if you misunderstand how that table is supposed to be
> constructed, in the case of DJGPP.  The C++ standard seems to
> have forgotten about the C specialty of passing EOF into a
> <ctype.h> library macro/function.

Bear in mind that that uses the hidden assumption that EOF == -1.

-- 
"If you want to post a followup via groups.google.com, don't use
 the broken "Reply" link at the bottom of the article.  Click on 
 "show options" at the top of the article, then click on the 
 "Reply" at the bottom of the article headers." - Keith Thompson

- Raw text -