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=2.2 required=5.0 tests=BAYES_20,INVALID_MSGID, PLING_QUERY,REPLYTO_WITHOUT_TO_CC 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: fred@genesis.demon.co.uk (Lawrence Kirby) Subject: Re: How big is an int? (was: Yet another stupid language war (was: ... the only languages you need!!)) Date: 1997/11/13 Message-ID: <879433137snz@genesis.demon.co.uk>#1/1 X-Deja-AN: 289255836 References: <879381995snz@genesis.demon.co.uk> X-Mail2News-User: fred@genesis.demon.co.uk X-Complaints-To: abuse@demon.net X-Mail2News-Path: genesis.demon.co.uk X-Trace: mail2news.demon.co.uk 879434483 22936 fred genesis.demon.co.uk Organization: none Followup-sTo: comp.lang.c,comp.lang.c++ Reply-To: fred@genesis.demon.co.uk Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.lang.java.advocacy Date: 1997-11-13T00:00:00+00:00 List-Id: In article <879381995snz@genesis.demon.co.uk> fred@genesis.demon.co.uk "Lawrence Kirby" writes: ... >Simply knowing a program is strictly conforming does not mean you can >predict what it will output. However if you do know what input a >strictly conforming program receives you should be able to predict from >the standard alone what output it generates (although I'm not 100% sure of >that). After sleeping on it it is fairly obvious that isn't true. You can't tell what output a program produces if a file output operation generates an error. Perhaps the most interesting case here is the automatic stream closing that happens at normal program termination, where the program itself never gets an indication that an error occurred. Nevertheless there's nothing in the standard that stops a program being strictly conforming because of that. This thread has been cross-posted to various non-C language newsgroups. Certainly this particular discussion is very C specific with possibly some relevance to C++. I'm therefore directing followups to comp.lang.c and comp.lang.c++ only. -- ----------------------------------------- Lawrence Kirby | fred@genesis.demon.co.uk Wilts, England | 70734.126@compuserve.com -----------------------------------------