Falsehoods programmers believe about undefined behaviour, https://predr.ag/blog/falsehoods-programmers-believe-about-undefined-behavior/.
The article explains what is an undefined behaviour exactly. It’s funny.
The basic problem with C is that the committee have been asleep at the wheel for 30 years. As soon as UB began to be interpreted as "the compiler will now do impossible things" they should have stepped in and said "actually we mean that _some value_ is produced, but we do not care to specify what" (or a trap is raised, to keep SGI on board). That covers arithmetic anyway.
Sure for pointers and longjmp you do need "truly undefined", but even that could be profiled.
1/
›They Have Played Us #Programmer|s for Absolute #Fool|s‹
🧷 https://www.youtube.com/watch?v=QTiAWZ1YfzI&t=217s
🌺
🏷️ #Lisp #Scheme #CommonLisp #CPP #Rust #DennisRitchie #BrianKernighan #BjarneStroustrup #CLang #Rustacean #MetaProgramming #Risitas #JohnMcCarthy #Unix #Pipes #Segfault #NullPointer #UndefinedBehaviour #GarbageCollection #MemoryManagement #BellLabs #ObjectSystem #FunctionalProgramming #Syntax #Rustaceans #MemorySafety #ElRisitas #CLOS #AMOP
#programmer #fool #lisp #scheme #commonlisp #cpp #rust #dennisritchie #briankernighan #bjarnestroustrup #clang #rustacean #metaprogramming #risitas #johnmccarthy #unix #pipes #segfault #NullPointer #undefinedbehaviour #garbagecollection #memorymanagement #belllabs #objectsystem #functionalprogramming #syntax #rustaceans #memorysafety #elrisitas #clos #AMOP