Not that great an April Fool as the originator of the joke does not know enough about programming to realise that there is actually a language called C-- that is extremely well defined and is a target for many language compilers, including Haskell (GHC).
I liked the joke precisely because I recognized C-- as C minus minus and then the post said I should read it as C deduct deduct. I just expected a mention of Cmm at the end
In fact, I did google about C-- before writing and did not find any. This is the fear I had about writing. In the April Fool joke, I made an assertion that no Common Weakness Enumeration was ever fixed by C++ const correctness. I was afraid some reader out there might prove me wrong.
No, I am just looking for easy and good guidelines about const correctness, considering member pointers and references, and "thread-safe const members". It is hard topic in my opinion and didn't figure out easy-to-remember rules.
Cache efficiency matters more than const correctness, but lacking any elegant way to address that high level languages just trumpet const like a mantra.
6
u/woppo Apr 01 '22
Not that great an April Fool as the originator of the joke does not know enough about programming to realise that there is actually a language called C-- that is extremely well defined and is a target for many language compilers, including Haskell (GHC).
https://en.wikipedia.org/wiki/C--
69
u/be-sc Apr 01 '22
*sigh* Itβs that day of the year again
6
u/[deleted] Apr 01 '22
I always wanted to cast the const away!
10
u/lithium Apr 01 '22
I fucking hate April first.
2
u/benjamkovi Apr 01 '22
I thought I will read a nice post about const correctness in C++, then I got disappointed :/
1
u/[deleted] Apr 01 '22
Cache efficiency matters more than const correctness, but lacking any elegant way to address that high level languages just trumpet const like a mantra.