Ifs and &&s and Plan 9's Source Code
computationallyendowed.com
Ifs and &&s and Plan 9's Source Code
1–10 of 150 posts
Re: Ifs and &&s and Plan 9's Source Code
#2C++ has "and"/"or"/"not" etc., so you can do
if(not A and B)
To get them in C, see the note about iso646.h in the link.
Re: Ifs and &&s and Plan 9's Source Code
#3As an idiom I quite like this form. I often do similar for double iterations:
for (int x = 0; x Re: Ifs and &&s and Plan 9's Source Code
#4This also provides an advantage when debugging. It will become immediately obvious which condition fails when stepping through the code. That isn't always the case with a long string of &&s.
Re: Ifs and &&s and Plan 9's Source Code
#5If not for the need to get and later free the
Dir *b; bool samefile(Dir *a, Dir *b)
Re: Ifs and &&s and Plan 9's Source Code
#6C++ has "and"/"or"/"not" etc., so you can do if(not A and B) but I'm not sure I've ever seen anyone do it. http://en.cppreference.com/w/cpp/language/operator_alternati... To get them in C, see the note about iso646.h in the link.
I don't think it really improves readability. All the programmers are familiar with && and ||, and using something else will just confuse people.
Also, it's not really that hard to #define it yourself, instead of using includes.
Re: Ifs and &&s and Plan 9's Source Code
#7Good luck using an auto formatter on a code base that uses this technique.
Re: Ifs and &&s and Plan 9's Source Code
#8C++ has "and"/"or"/"not" etc., so you can do if(not A and B) but I'm not sure I've ever seen anyone do it. http://en.cppreference.com/w/cpp/language/operator_alternati... To get them in C, see the note about iso646.h in the link.
I don't think it really improves readability. All the programmers are familiar with && and ||, and using something else will just confuse people. Also, it's not really that hard to #define it yourself, instead of using includes.
I definitely wouldn't use them because they are unfamiliar. However, in my head I pronounce "&&" as "and" and "&" as "bitand", so using and/bitand over &&/& would reduce a depressingly not-uncommon typo for me. However, on balance, not worth it to me.
Note that in C++ they are keywords which is superior to macros.
Re: Ifs and &&s and Plan 9's Source Code
#9When you use the fact that && is not the logical conjunction, you'd better use another if.
if (b != nil)
if (b->bla == a->bla)
if (b != nil && b->bla == a->bla)Re: Ifs and &&s and Plan 9's Source Code
#10As an idiom I quite like this form. I often do similar for double iterations: for (int x = 0; x
[deleted]