RE: Is this a gcc bug?

[David Korn <dkorn at pixelpower dot com>]

>> > How about something like:
>> >         warning: 'x' may have unexpected value because of 
>side-effects
>> > or
>> >         warning: side-effects make value of 'x' undefined
>> > or
>> >         warning: undefined order of side-effects on 'x'
>> > One might replace "side-effects" by "updates" or "changes to".
>> 
>> How about, multiple side-effects on 'x' between sequence points?
>
>"sequence points" is standardese and doesn't mean anything to 
>most users.
>Even "side-effects" may be surprising -- I don't think a user thinks
>of the increment of x in x++ as a "side effect".
>
>How about:
>
>warning: the order of the modifications to 'x' is undefined

  How about:

warning: extra-nasal demons invoked on line #xxx, please report to 
comp.lang.c to be flamed.

       DaveK  <g>

ps. Of course, we'd be within the language spec to emit code to format the
user's hard drive at that point, but let's be merciful. Maybe it should
just kick off nethack, or compile a quick version of wumpus or somesuch....
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************