Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Implicit int becoming errors is going to break certain IOCCC entries, including some more recent entries that might have done it due to size constraints, for example:

https://www.ioccc.org/years.html#2019_burton

https://www.ioccc.org/years.html#2019_duble



You can still compile these by downgrading the errors to warnings. They are just errors-by-default now.


Not hostile toward it, but -- if the IOCCC ceased tomorrow, the world would be neither better nor worse off for the loss (in the grand scheme).


I think it best we keep the folks who like to write that sort of C code busy with the IOCCC rather than out coding in the real world!

/s




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: