OK, I think I see what SHOULD happen here. It's been forever since I've actually... | Hacker News

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

		mjevans on Feb 15, 2017 \| parent \| context \| favorite \| on: I Do Not Know C: Short quiz on undefined behavior ... OK, I think I see what SHOULD happen here. It's been forever since I've actually compiled a C program not part of some package I was installing, BUT. * There should be a warning flag, and it should be ON BY DEFAULT, that //all// code removal is stated, and the logic behind it given. * It should be possible to elevate that condition to an error (and that too might even be the default).

maxlybbert on Feb 15, 2017 [–]

I have no idea if it's true, but compiler implementers swear that their compilers perform so many optimizations, and that those optimizations allow additional optimizations, that this kind of approach would bury you in messages.

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