| |||||||||||||
pr_unwanted()?pr_unwanted()?Posted Dec 24, 2009 9:21 UTC (Thu) by liljencrantz (subscriber, #28458)In reply to: pr_unwanted()? by flewellyn Parent article: pr_unwanted()?
Less typing and more explicit code sounds like two very reasonable reasons to use a bit of code to me.
(Log in to post comments)
pr_unwanted()? Posted Dec 24, 2009 16:31 UTC (Thu) by grmd (subscriber, #4391) [Link]
The trouble is it's the thin end of the wedge; it's not any more specific,
and it means that developers needlessly have something extra to learn.
Having worked on project that layer macros upon macros it rapidly becomes a
pr_unwanted()? Posted Dec 24, 2009 19:14 UTC (Thu) by vonbrand (subscriber, #4458) [Link] "More explicit" as long as there are very few functions/macros around. If there are more than a dozen, you start wondering if what you think it does is right... and the kernel is already huge, with its own set of non-standard stuff and rules. Better leave them out.
|
|||||||||||||