So as not to break if...else statements. A macro *looks* like a function
call, and so people are going to put a ";" after it. Thus, the macro needs
a good way to eat that ";" that will keep the whole thing as one statement.
--Tim Smith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu