News for hackers. Stuff that matters.
Re:Retiring a Favourite C++ Joke by dvh on Friday March 17, 2023 @02:47AM (#35194032)
I made this compiler joke and received whoping 930 upvotes for it: https://i.redd.it/dp6ixt4ri1hz.png
Re:Retiring a Favourite C++ Joke by FpUser on Friday March 17, 2023 @07:03AM (#35195432)
LOL. Loved it
Re:Retiring a Favourite C++ Joke by secondcoming on Friday March 17, 2023 @08:31AM (#35196219)
Ha! It actually took me far too long to get it!
Re:Retiring a Favourite C++ Joke by fatcow on Friday March 17, 2023 @10:11AM (#35197311)
Why is it funny, please explain?
Re:Retiring a Favourite C++ Joke by jmaygarden on Friday March 17, 2023 @10:18AM (#35197422)
It is the error message you often get when creating a password.
Re:Retiring a Favourite C++ Joke by fatcow on Friday March 17, 2023 @10:27AM (#35197558)
Yes I get that, didn't quite understand why this switching of error message is relevant to the code...
Re:Retiring a Favourite C++ Joke by kps on Friday March 17, 2023 @10:45AM (#35197783)
I thought it was funny because I've seen similar complaints from linters, e.g. clang-tidy's readability-identifier-length plus readability-identifier-naming, or pylint's invalid-name. (clang-tidy at least is smart enough to exempt loop counters.)
Re:Retiring a Favourite C++ Joke by isaacremuant on Friday March 17, 2023 @10:46AM (#35197797)
Jokes often work with subverting expectations. In this case you're surprised by a message that doesn't belong and then you remember where it comes from and likely relate it with how frustrating those ever changing rules can be.

That's why the joke works.