> > I think we should make "error()" just die. Continuing was fine > back in the > old days when we had tons of bogus errors, but there's little point to it > any more, I suspect. > > Linus >
That should be just fine but I see that at many places "warning()" is used instead of "error()". For example, sparse is calling "warning()" for missing semicolon, etc. Also, I see that many places in preprocess.c and parse.c, "warning()" is called instead of "error()". -Mitesh - To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
