From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6bf9d4ba0cfd8cb6 X-Google-Attributes: gid103376,public From: Hyman Rosen Subject: Re: Announce: OpenToken 2.0 released Date: 2000/02/07 Message-ID: #1/1 X-Deja-AN: 582668058 Sender: hymie@calumny.jyacc.com References: <3890C62B.18309585@telepath.com> <876unj$jcs$1@nnrp1.deja.com> <87d7qck6pm.fsf@deneb.cygnus.argh.org> X-Complaints-To: abuse@panix.com X-Trace: news.panix.com 949935629 23318 209.49.126.226 (7 Feb 2000 15:00:29 GMT) Organization: PANIX Public Access Internet and UNIX, NYC NNTP-Posting-Date: 7 Feb 2000 15:00:29 GMT Newsgroups: comp.lang.ada Date: 2000-02-07T15:00:29+00:00 List-Id: Florian Weimer writes: > Unfortunately, this becomes inband signalling on some platforms (where > sizeof(char) == sizeof(int)). Broken as designed. No. It's only in-band if on those platforms, input characters do in fact range over the full set of representable values of a char. Just because the compiler internally represents char with the same range as int does not mean that stream input is reading objects of that range from its sources. Input could be octets, or 16-bit unicode chars, or 32-bit other representation of input. It is usually the case that the wider character formats have error values which explicitly represent no character within the set, so that an out-of-band value may be supplied that way.