"If new true friend not protected for explicit private union, break case and try using this."
I often write
if (not ...
for emphasis. The "bitand" etc. are similarly useful where the operator might otherwise be mistaken for "&&" or, particularly, "||".
The only one that is an unfortunate choice is "compl", which just looks strange. When I feel a need to call attention to use of "~", I define a lambda "bitwise_not(bool)". But rarely.
A valid opinion for language design, but when writing real C++ code, I'd stick to the usual way of doing things.
English language keywords aren't always great for readability in my opinion. Ada's and then / or else syntax, for instance. They're the short-circuit syntax, whereas and and or give eager evaluation. [0] You can't determine that just from the syntax though, so it ends up being no less cryptic than using strange symbols the way C++ (typically) does.
It's like Van Halen and the brown M&Ms thing. It determines if the author of a C++ lexer, syntax highlighter, etc., read the Standard. Try splitting a digraph with \ and a newline.
Back in 2009 or so, I and a few others ran a Google-internal April Fool's prank based on this.
We auto-generated a humongous pull request for the Chromium source code and sent it out for review by all the various source code "owners" (super reviewers) who would need to sign off.
The change used the alternate encoding for curly and square brackets, claiming the original characters were inaccessible on an Icelandic keyboard layout (which is half true, and there were quite a few of us Icelanders around) and that therefore, to be inclusive, we would like to standardize on the alternative representation.
Good fun, although I don't remember if a single one of the reviewers was fooled :)
I've never seen anyone use these since they appeared in the spec decades ago. They're as pointless as trigraphs, which I've never seen in the wild either.
While I agree C++ is huge, I doubt anyone would survive a Python, Java, C#, VB.NET, JavaScript, Typescript, Fortran, Ada, Common Lisp, COBOL, C pub quiz, based on the very latest language versions.
One thing is, for the longest time MSVC did not support them (against the spec like always) so they could not be used if you wanted cross-platform code.
27 comments
[ 4.0 ms ] story [ 75.4 ms ] thread"If new true friend not protected for explicit private union, break case and try using this."
I often write
for emphasis. The "bitand" etc. are similarly useful where the operator might otherwise be mistaken for "&&" or, particularly, "||".The only one that is an unfortunate choice is "compl", which just looks strange. When I feel a need to call attention to use of "~", I define a lambda "bitwise_not(bool)". But rarely.
https://en.cppreference.com/w/cpp/utility/functional/bit_not
And I find its harder to typo and misread it:
`a && b || c` vs `a & b | c`
`a and b or c` vs `a & b | c`
English language keywords aren't always great for readability in my opinion. Ada's and then / or else syntax, for instance. They're the short-circuit syntax, whereas and and or give eager evaluation. [0] You can't determine that just from the syntax though, so it ends up being no less cryptic than using strange symbols the way C++ (typically) does.
[0] https://en.wikibooks.org/wiki/Ada_Programming/Operators#Shor...
Its explained in the first two sentences of the page.
I am just surprised I’ve never seen this in any code base before.
We auto-generated a humongous pull request for the Chromium source code and sent it out for review by all the various source code "owners" (super reviewers) who would need to sign off.
The change used the alternate encoding for curly and square brackets, claiming the original characters were inaccessible on an Icelandic keyboard layout (which is half true, and there were quite a few of us Icelanders around) and that therefore, to be inclusive, we would like to standardize on the alternative representation.
Good fun, although I don't remember if a single one of the reviewers was fooled :)
https://digitalmars.com/sargon/halffloat.html
I haven't seen it used in C++, though my C++ experience post this feature is limited.
While I agree C++ is huge, I doubt anyone would survive a Python, Java, C#, VB.NET, JavaScript, Typescript, Fortran, Ada, Common Lisp, COBOL, C pub quiz, based on the very latest language versions.