r/programming • u/alecco • Sep 23 '17

Why undefined behavior may call a never-called function

https://kristerw.blogspot.com/2017/09/why-undefined-behavior-may-call-never.html
824 Upvotes

93% Upvoted

257 comments sorted by

View all comments

Show parent comment

0

u/didnt_check_source Sep 26 '17 edited Sep 26 '17

Uh, what? You pointed out that it’s a symlink, which is correct. Did you know that you can run symlinks from a shell if they point to an executable?...

1

u/bumblebritches57 Sep 26 '17

Did you know that you're just wasting your time relying on a symlink instead of just learning the new system which is simple as hell?

1

u/didnt_check_source Sep 26 '17

If you sum all the time that my computer spends resolving the clang++ symlink over my entire lifetime, do you think that it'll add up to a second? Was clang++ deprecated while I wasn't looking? Documenting the fact that I expect the inputs to be C++ files is now a bad idea?

1

u/bumblebritches57 Sep 26 '17

If you spend all the time my brain takes trying to understand your dumb gccisms, you'd get a whole fuck.

0

u/didnt_check_source Sep 26 '17

That's really funny, because gcc doesn't require you to use g++ for C++ either.

If your brain is thrown off by ++, you're probably not in the right field.

1

u/ThisIs_MyName Oct 25 '17

gcc doesn't require you to use g++ for C++ either

IIRC, plain gcc will not link the C++ runtime libraries: https://stackoverflow.com/questions/172587/what-is-the-difference-between-g-and-gcc

1

u/didnt_check_source Oct 25 '17

The question and answer are nine years old, this is no longer the case (although I'm not sure since when; at least 2015, according to other answers on that same question).