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: dvdeug@x8b4e53cd.dhcp.okstate.edu (David Starner) Subject: Re: Announce: OpenToken 2.0 released Date: 2000/02/01 Message-ID: <87799k$aai1@news.cis.okstate.edu>#1/1 X-Deja-AN: 580467216 References: <3890C62B.18309585@telepath.com> <876unj$jcs$1@nnrp1.deja.com> Organization: Oklahoma State University User-Agent: slrn/0.9.6.2 (Linux) Reply-To: dstarner98@aasaa.ofe.org Newsgroups: comp.lang.ada Date: 2000-02-01T00:00:00+00:00 List-Id: On 01 Feb 2000 13:16:14 -0500, Hyman Rosen wrote: >By the way, the normal C/C++ style for handling EOF is to have the >return type of the character reader be such that it can hold any >value of the character set, plus an out-of-band value representing >EOF. The usual is '#define EOF -1' and 'int getchar()'. Which means that c: Character; c := getchar(); is illegal (at least in Ada; in C it would get silently truncated.) It's a major pain in C, and a well known source of bugs. How about making it like procedure GetChar (EOF: in out boolean; Char: in out character);? -- David Starner - dstarner98@aasaa.ofe.org If you wish to strive for peace of soul then believe; if you wish to be a devotee of truth, then inquire. -- Friedrich Nietzsche