Jeff Haran wrote:
I suppose as an alternative you could go way against the usual practice and put some text in a function header comment block indicating what the return code means. I know it doesn't get used much but C has had this /* comment */ thing for a long time. I've never understood why more people don't use it.
All true. I guess I could go the full hog and document the entire
function, then use "return false" as Jozsef suggested, but this will
stick out as a sore thumb as it will be the only function documented in
the entire module.
Jozsef, I don't mind doing either of the suggested alternatives: keep
"goto err" or document the entire function and use "return false" - let
me know what your preference is.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
