relational operators on pointers

[James Hu]

3.4.3 covers it nicely.

I find no mention of "eventually a computer will explode" in that
paragraph.

It doesn't even imply that out of an infinite set of computers, one
will explode if UB is invoked.

And furthermore, if a C program is invoking UB, it is not a strictly
conforming program.

Please stop trolling.



-- James

 

[Richard Heathfield]

Chapter and verse please!

Since it is well-known that UB is an abominable thing to invoke, and since
everybody who has ever watched a science fiction movie knows that fire
makes computers explode (irrespective of the presence or absence of, say,
Semtex or a large bottle of nitroglycerine within the computer's casing), I
suspect that Revelation 21:8 satisfies your requirement for chapter and
verse.

 

[Mark McIntyre]

I find no mention of "eventually a computer will explode" in that
paragraph.

It clearly says that undefined behaviour is anything not defined by
the standard. Exploding computers are not defined by the standard. So
therefore they're covered by this section.

It doesn't even imply that out of an infinite set of computers, one
will explode if UB is invoked.

It also doesn't say that your machine will print an error
"segmentation fault: core dumped" or "this program has performed an
illegal instruction" or "a small blue fish has just flown out of your
nostril".
So what?

Please stop trolling.

Stop yourself...

 

[Mark McIntyre]

I suspect that Revelation 21:8 satisfies your requirement for chapter and
verse.

Presumably the Authorised Version as revised by CLC now reads:

"But for the cowardly, unbelieving, sinners, abominable, murderers,
sexually immoral, sorcerers, idolaters, and all users of undefined
behaviour, their part is in the lake that burns with fire and sulfur,
which is the second death."

 

[Dave Thompson]

On Sat, 13 Dec 2003 11:46:37 +0000 (UTC), Richard Heathfield

Since it is well-known that UB is an abominable thing to invoke, and since
everybody who has ever watched a science fiction movie knows that fire
makes computers explode (irrespective of the presence or absence of, say,
Semtex or a large bottle of nitroglycerine within the computer's casing), <snip>

When has fire ever caused a computer to explode? What movie/TV fire
causes is the rapid failure of physical structures, preferentially
downward even in space, usually while not injuring people in the same
room beyond depositing some soot on them.

(Unless you mean "fire" in the military sense of shooting at it. That
causes even inert things to explode.)

What mostly causes explosion of computers, or rather usually displays
including (noncomputer) data and even video monitors, is a physical
impact at some remote location on the sensors or other peripherals
connected electronically or virtually to the monitor(s), or less often
the input of invalid data and/or unauthorized commands.

- David.Thompson1 at worldnet.att.net

 

[Christopher Benson-Manica]

"But for the cowardly, unbelieving, sinners, abominable, murderers,
sexually immoral, sorcerers, idolaters, and all users of undefined
behaviour, their part is in the lake that burns with fire and sulfur,
which is the second death."

Other than the fact that void main() is omitted, that seems reasonable
to me.

 

[xarax]

On Sat, 13 Dec 2003 11:46:37 +0000 (UTC), Richard Heathfield

When has fire ever caused a computer to explode? What movie/TV fire
causes is the rapid failure of physical structures, preferentially
downward even in space, usually while not injuring people in the same
room beyond depositing some soot on them.

(Unless you mean "fire" in the military sense of shooting at it. That
causes even inert things to explode.)

What mostly causes explosion of computers, or rather usually displays
including (noncomputer) data and even video monitors, is a physical
impact at some remote location on the sensors or other peripherals
connected electronically or virtually to the monitor(s), or less often
the input of invalid data and/or unauthorized commands.

Or installing Windows...

 

[Robert Stankowic]

casing),


Or installing Windows...

Or installing *nux - it does seldom cause the computer to explode, but
forgets the mouse, doesn't use DMA if not told explicitely.. and sometimes
at release 69255.1024.1234 it even may..... er - hm

Sorry, could not resist :^/
Robert