* Julia Lawall <julia@xxxxxxx> wrote: > There are some legitimate uses of !x & y which are actually of the > form !x & !y, where x and y are function calls. That is a not > particularly elegant way of getting both x and y to be evaluated and > then combining the results using "and". If such code is considered > acceptable, then perhaps the sparse patch should be more complicated. i tend to be of the opinion that the details in C source code should be visually obvious and should be heavily simplified down from what is 'possible' language-wise - with most deviations and complications that depart from convention considered an error. I'd consider "!fn1() & !fn2()" a borderline coding style violation in any case - and it costs nothing to change it to "!fn1() && !fn2()". Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
