Xref: news2.mv.net comp.lang.c:56549 comp.lang.c++:72618 comp.os.msdos.djgpp:1128 comp.std.c:4753 gnu.g++.help:4637 gnu.gcc.help:5829 From: rfg AT monkeys DOT com (Ronald F. Guilmette) Newsgroups: comp.lang.c,comp.lang.c++,gnu.gcc.help,gnu.g++.help,comp.os.msdos.djgpp,comp.std.c Subject: Re: float != float and floats as return types Date: 15 Feb 1996 01:28:49 -0800 Organization: Infinite Monkeys & Co. Lines: 30 Message-ID: <4fuuch$6db@segfault.monkeys.com> References: <4ej9lb$mpc AT fu-berlin DOT de> <4ettr4$al5 AT der DOT twinsun DOT com> NNTP-Posting-Host: segfault.monkeys.com To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp In article , Tanmoy Bhattacharya wrote: > >Note that I have added comp.std.c to the list of newsgroups. > >In article <4ettr4$al5 AT der DOT twinsun DOT com> eggert AT twinsun DOT com (Paul >Eggert) writes: > > That being the case, I think it wise for users not to rely on the fine > points here, and my advice to the GCC implementers is to hold off on > changing GCC's behavior until the C Standard committee acts. > >I, on the other hand, think that the current standard ought to be >interpreted to mean that truncation is needed. Claiming that it is not >needed is relying on the fine points. That is purely a personal >opinion. No. It is just plain right. The standard is entirely clear that assignment and casting are two cases where a compiler is required to change the precision/representation of an FP value exactly as called for by the type of the cast or by the type of the expression on the left hand side of the assignment. There is nothing in the least bit vague about this. Those are the rules. -- -- Ron Guilmette, Roseville, CA -------- Infinite Monkeys & Co. ------------ ---- E-mail: rfg AT monkeys DOT com ----------- Purveyors of Compiler Test Suites - ------ Copyright (c) 1996 by Ronald F. Guilmette; All rights reserved. -----