[lkml]   [2004]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: (0 == foo), rather than (foo == 0)
    Date writes:
    >> As a result, using the former just tends to increase peoples
    >> confusion by making code harder to read, which in turn tends
    >> to increase the chance of bugs.
    >Kindly don't insult the kernel developers' with such statements. ;-)
    >They are smart enough to understand such constructs [...]

    It's not about intelligence! It's about the nature of human visual
    pattern-matching. Reading a pattern is always easier when you've seen
    it thousands of times before.

    Henry Spencer's dictum about brace style seems particularly apropos:

    8. Thou shalt make thy program's purpose and structure clear to thy
    fellow man by using the One True Brace Style, even if thou likest
    it not, for thy creativity is better used in solving problems than
    in creating beautiful new impediments to understanding.

    And that's what "0 == foo" is: an impediment to understanding.
    Chip Salzenberg - a.k.a. - <>
    "I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early." // MST3K
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:01    [W:0.300 / U:2.408 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site