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,9c86eb13dd395066 X-Google-Attributes: gid103376,public From: Jim Balter Subject: Re: CRC in Ada? Date: 1997/03/10 Message-ID: <332491B5.7E7E@netcom.com>#1/1 X-Deja-AN: 224511049 References: <1997Mar2.220652@nova.wright.edu> <1997Mar6.091150.1@eisner> Organization: JQB Enterprises X-NETCOM-Date: Mon Mar 10 4:58:58 PM CST 1997 Newsgroups: comp.lang.ada Date: 1997-03-10T16:58:58-06:00 List-Id: Robert Dewar wrote: > > Ole-HJ said > > < especially as functions to explicitly control the buffering and flush > the buffer is part of the specification.>> > > YOu have lost me here, what do you mean when you say that functions to > explicitly control the buffering are part of the speciication. Yes > there is flush, but that's it ... No, there is no flush, but there is fflush, and setbuf, setvbuf, _IOFBF, _IOLBF, _IONBF, and BUFSIZ are all part of the specification; it really helps if one limits one's authoritative claims to what one actually knows something about. While it is true that an ANSI C stdio implementation can send bytes by bicycle courier, "quality of implementation" mandates against it. Byte-at-a-time C (or in fact POSIX, and thus ADA, given a binding) programs perform well portably, a fact that no amount of sophistry can cancel. --