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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, PLING_QUERY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fdb77,4873305131bf4d94 X-Google-Attributes: gidfdb77,public X-Google-Thread: 1014db,4873305131bf4d94 X-Google-Attributes: gid1014db,public X-Google-Thread: 103376,4873305131bf4d94 X-Google-Attributes: gid103376,public X-Google-Thread: 109fba,4873305131bf4d94 X-Google-Attributes: gid109fba,public From: Dan.Pop@cern.ch (Dan Pop) Subject: Re: How big is an int? (was: Yet another stupid language war (was: ... the only languages you need!!)) Date: 1997/11/10 Message-ID: #1/1 X-Deja-AN: 288436567 Sender: news@news.cern.ch (USENET News System) X-Nntp-Posting-Host: ues5.cern.ch References: <34557f2b.1934172@news.mindspring.com> <63qkp9$bqr$3@darla.visi.com> <63r2sv$rgm$1@helios.crest.nt.com> <878820761snz@genesis.demon.co.uk> <63t1j9$md8$1@helios.crest.nt.com> <873814384snz@genesis.demon.co.uk> Organization: CERN European Lab for Particle Physics Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.lang.java.advocacy Date: 1997-11-10T00:00:00+00:00 List-Id: In <873814384snz@genesis.demon.co.uk> fred@genesis.demon.co.uk (Lawrence Kirby) writes: >In article Dan.Pop@cern.ch "Dan Pop" writes: > >>Can a strictly conforming program perform *any* kind of I/O? > >Yes. Please provide an example. >> Part >>of the definition of "strictly conforming program" says: >> >> It shall not produce output dependent on any unspecified, undefined, or >> implementation-defined behavior... > >However that doesn't mean that a strictly conforming program has to produce >the same output every time you run it. If that were true a program which >wrote output derived from rand() could not be strictly conforming (and it >can). Nope, it cannot. The behaviour of rand() is unspecified. Also code using floating point arithmetic or most of the functions from cannot be strictly conforming. >>It is unspecified (or maybe implementation-defined) when an I/O operation >>fails and if that failure affects the behaviour of your program... > >No, it isn't. The standard states explicitly all cases of unspecified and >implementation-defined behaviour, these terms are very specific. >Only undefined behaviour can result from a lack of definition, and even >then only from a *total* lack of definition (or there is a defect in the >standard). getc() (for example) has no unspecified and no >implementation-defined behaviour (*). You missed the point. It is undefined when the well defined conditions that lead to the failure of a stdio function occur. But the behaviour of the program depends on the occurence of these conditions. Dan -- Dan Pop CERN, IT Division Email: Dan.Pop@cern.ch Mail: CERN - PPE, Bat. 31 1-014, CH-1211 Geneve 23, Switzerland