From -2381019688097890139 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10f5bc,6f6e97a6fdbbf44c X-Google-Attributes: gid10f5bc,public X-Google-Thread: 110292,6f6e97a6fdbbf44c X-Google-Attributes: gid110292,public X-Google-Thread: 109fba,6f6e97a6fdbbf44c X-Google-Attributes: gid109fba,public X-Google-Thread: 1149ec,6f6e97a6fdbbf44c X-Google-Attributes: gid1149ec,public X-Google-Thread: 102b75,6f6e97a6fdbbf44c X-Google-Attributes: gid102b75,public X-Google-Thread: f78e5,6f6e97a6fdbbf44c X-Google-Attributes: gidf78e5,public X-Google-Thread: 1014db,6f6e97a6fdbbf44c X-Google-Attributes: gid1014db,public From: abdella@egertp.ericsson.se (R. Abdella) Subject: Re: And you thought that the Pentium bug was bad! (Get a load of this!) Date: 1995/06/23 Message-ID: #1/1 X-Deja-AN: 104873975 references: <3s2las$1br@hustle.rahul.net> <3s46bi$3qe@devel.dvstsol.demon.co.uk> <3sbm5j$vuq@locutus.rchland.ibm.com> <3scr34$smm@fg70.rz.uni-karlsruhe.de> organization: Ericsson Inc. newsgroups: comp.std.c,comp.std.c++,comp.lang.c,comp.lang.c++,comp.sys.intel,comp.arch,comp.software.testing In article <3scr34$smm@fg70.rz.uni-karlsruhe.de> ig25@fg70.rz.uni-karlsruhe.de (Thomas Koenig) writes: [snip] >>Jonathan Allan replied: >>> Ah! The dreaded "Don't *DO* that!" answer. >>Exactly. The C standard is bad enough, with "undefined" in so places, >>without perfectly legal constructs being unusable too. >It's legal, but it's far from good style; there is no use for this kind >of games with scopes, unless you WANT to be unclear. I fully agree! I simply do not see the what all the fuss is about. Yes it is a bug, but IMO a very minor bug because this is extremely poor style, and unless you are into writing poorly styled code, you should never see this. >Could you have told with certainty, and without looking at the C >standard, what this particular piece of code (even with the forgotten >) was supposed to have done? If so, I congratulate you on >your kills in arcane corners of the C standard. Especially as a person coming into maintain this code. This code *could* make it impossible to determine which variable 'd' the original developer *intended* on using in the printf, *regardless* of whether this is standardized or not. To 'borrow' the phrase from Nike, I would say 'Just *don't* do it'. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ R. Abdella abdella@egertp.ericsson.se ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The opinions expressed here do not belong to any person, organization, entity, or element - other than myself... (of course) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~