in reply to Re: The behavior is [sic] undefined
in thread The behavior is [sic] undefined

"And, if I do X, what is the resulting behavior?"

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^3: The behavior is [sic] undefined
by JavaFan (Canon) on May 19, 2009 at 00:25 UTC
    We haven't specified that, so the behavour will be defined by the implementations.
    That's typically labelled as implementation defined. Which is not the same as undefined behaviour.
[reply]
[reply]
        Specification of language X says:
        1. The behaviour of ~0 is implementation defined, but may not be positive.
        2. The behaviour of 0^0 is undefined.
        Implementation S specifies that ~0 equals -1. Implementation T specifies that ~0 equals 1. Neither defines what 0^0 means. Program P contains ~0. Program R contains 0^0. Running P on S produces -1. Running R on S locks up the OS requiring a reboot. S is confirming. Running P on T produces 1. Running R on T produces an error message. T is not confirming.

        Implementation defined means that the feature is a valid feature, and it's up to each implementation to define what it means. Undefined behaviour basically means the feature is not valid, and implementations do not define what happens.

        But let me guess, you're still going to claim to not understand the difference, right?

[reply]

In Section Meditations