Re:Boringcc: Proposal for a C compiler for secure software
by kenko on Monday December 21, 2015 @04:32PM
(#10773672)
Why is that more appropriate than just defining all the currently undefined/implementation-specific behavior?
[ Parent
| on HN ]
Re:Boringcc: Proposal for a C compiler for secure software
by CountSessine on Monday December 21, 2015 @04:40PM
(#10773721)
IMO both approaches would be useful. One nice thing about outlawing undefined behaviour rather than defining it, though, it that you'll be writing portable code - if you have a code base that's filled with all all sorts of once-was-undefined-but-now-is-defined behaviour, you can never build that code on another compiler.