| |||||||||||||
Solution: Don't use C.Solution: Don't use C.Posted May 16, 2011 16:14 UTC (Mon) by benjamingeer (guest, #67678)Parent article: What every C Programmer should know about undefined behavior #2/3
Really. There are so many better languages.
(Log in to post comments)
Solution: Don't use C. Posted May 16, 2011 16:25 UTC (Mon) by felixfix (subscriber, #242) [Link]
There are not very many more naive statements.
Solution: Don't use C. Posted May 16, 2011 18:34 UTC (Mon) by rpbrennan (guest, #70904) [Link]
Ahhh, the sweet sound of someone being served....
Solution: Don't use C. Posted May 16, 2011 19:29 UTC (Mon) by renox (subscriber, #23785) [Link]
Apparently you missed the part of the articles which explains that many of C's undefined behaviours allow the compiler to make better optimisations..
This doesn't mean that one should use C: premature optimisation is still the root of all evil, but just that the reaction "undefined behaviour == don't use C" is naive at best.
|
|||||||||||||