On Tuesday 12 February 2013, Paul Mundt wrote: > > While I do get the point... I chatted with Grant about it and > > I want to talk to some toolchain people about this to see if > > pointers containing potential error codes can somehow be > > "flagged" by the compiler so we can enforce error checking on > > them. (It may sound a bit utopic...) > > > At the very least you can __must_check annotate, although that's probably > still a bit coarser grained than what you're after. There is an idea: we could have variants of __must_check for different classes of returns: NULL error, ERR_PTR, negative integer on error, ... Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
