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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC 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: Florian Weimer Subject: Re: Announce: OpenToken 2.0 released Date: 2000/02/07 Message-ID: <87ya8wok07.fsf@deneb.cygnus.argh.org>#1/1 X-Deja-AN: 582804617 References: <3890C62B.18309585@telepath.com> <876unj$jcs$1@nnrp1.deja.com> <87d7qck6pm.fsf@deneb.cygnus.argh.org> Mail-Copies-To: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@cygnus.argh.org X-Trace: deneb.cygnus.argh.org 949953976 2539 192.168.1.2 (7 Feb 2000 20:06:16 GMT) Organization: Penguin on board User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.4 Mime-Version: 1.0 Reply-To: Florian Weimer NNTP-Posting-Date: 7 Feb 2000 20:06:16 GMT Newsgroups: comp.lang.ada Date: 2000-02-07T20:06:16+00:00 List-Id: Hyman Rosen writes: > 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. You are right for text files. For binary files, there has to be a bijection between the internal and external representation of characters. This means that the value EOF can occur in a binary stream if sizeof(char) equals sizeof(int).