Undefined behaviour in C23

In the SEI CERT C Soding Standards we read:


"According to the C Standard, Annex J, J.2 [ISO/IEC 9899:2024],
the behavior of a program is undefined in the circumstances outlined
in the following table."


The table has 221 numbered cases and can be found here:


<https://wiki.sei.cmu.edu/confluence/display/c/CC.%2BUndefined%2BBehavior>


According to the C Standard Committee (paraphrasing) "You may eat
from any tree in the garden of coding, except for any of the 221
trees of undefined behaviour. If you eat from any of the 221 trees
of undefined behaviour your program may die, either immediately or at
some unspecified time in the future, or may do absolutely anything at
any future time. You must study the Book of the Knowledge of Defined
and Undefined (the 758 page C23 standard document) to learn exactly
how to recognise each of the 221 trees of undefined behaviour.
Please pay the cashier $250.00 to purchase a copy of the Book
of the Knowledge of Defined and Undefined".




\--
Martin


Dr Martin Ward | Email: [martin@gkc.org.uk](mailto:martin@gkc.org.uk) | <http://www.gkc.org.uk>
G.K.Chesterton site: <http://www.gkc.org.uk/gkc> | Erdos number: 4
[When a language is 50 years old and there is a mountain of legacy code that
they really don't want to break, it accumulates a lot of cruft. If we were
starting now we'd get something more like Go.


On the other hand, there's the python approach in which they deprecate and
remove little used and crufty features, but old python code doesn't work any
more unless you go back and update it every year or two. -John]

Return to the comp.compilers page.
Search the comp.compilers archives again.