Annotated edit history of
UndefinedSemantics version 5, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 5 |
AristotlePagaltzis |
1 |
Standardised languages often have "grey areas" - features or (combinations of) conditions for which no behaviour was defined. Any implementation of the standard may react however it sees fit when it encounters such a condition, either because implementors were explicitly granted such freedom by the standardisation committee, or simply out of necessity because the committee couldn't agree on a single behaviour or just plain overlooked this condition. |
| 1 |
StuartYeates |
2 |
|
| 2 |
AristotlePagaltzis |
3 |
Examples of UndefinedSemantics include |
| 1 |
StuartYeates |
4 |
|
| 2 |
AristotlePagaltzis |
5 |
* native method calls in [Java] |
| |
|
6 |
* #pragma defines in [C]/[C++] |
| |
|
7 |
* many features of [HTML] |
| |
|
8 |
|
| 5 |
AristotlePagaltzis |
9 |
Note that UndefinedSemantics means exactly that, if you add __#pragma explode__ to your [C] program, you are not allowed to be surprised that your toilet exploded. |
