News for hackers. Stuff that matters.
Re:Ifs and &&s and Plan 9's Source Code by chj on Friday May 24, 2013 @09:29PM (#5766045)
Using ifs is definitely more readable than &&, words always win. However carefully alignment of && and ( can make things better. Note that the comment after "if" is necessary to keep the shape balanced.

    if( /* b is same as a */
           (b != nil)
        && (b->qid.type == a->qid.type)
        && (b->qid.path == a->qid.path)
        && (b->qid.vers == a->qid.vers)
        && (b->dev == a->dev)
        && (b->type == a->type)
    ){
        fprint(2, "cp: %s and %s are the same file\n", an, bn);
        ret = 1;
    }
Re:Ifs and &&s and Plan 9's Source Code by dllthomas on Saturday May 25, 2013 @10:33AM (#5767372)
"words always win"

Add seven to three then multiply the whole thing by twelve.

(7 + 3) * 12

Re:Ifs and &&s and Plan 9's Source Code by dave809 on Saturday May 25, 2013 @04:04PM (#5768633)
(mult (add seven three) twelve)
Re:Ifs and &&s and Plan 9's Source Code by dllthomas on Saturday May 25, 2013 @04:24PM (#5768692)
Better, obviously, but I think the regular math notation still wins. It's more concise, and equally (if not more) familiar.
Re:Ifs and &&s and Plan 9's Source Code by moron4hire on Saturday May 25, 2013 @03:00PM (#5768368)
only if you treat symbols as a foreign language