On 2/14/2014 12:14 PM, John Hardin wrote:
On Fri, 14 Feb 2014, Kevin A. McGrail wrote:
On 2/14/2014 10:54 AM, John Hardin wrote:
On Fri, 14 Feb 2014, Kevin A. McGrail wrote:
> > Makes sense. if you want to submit a patch for the dbg with an
if > version 3.3.2 or greater ... don't debug,
Wouldn't that be equivalent to "if (0) debug" ?
This warning is more for the rule developers so that they can put
"if (version >= 3.003002)" around the problematic rule. If there
was some
way to suppress it except during a full make, that might be a better
solution than version checks. Would dbg() do that?
Good point. I think you can remove the code. It won't apply in
anything after 3.3.2 clearly.
Do we want to be aware of creating rules that may cause problems for
pre-3.3.2 installs? As I said, the primary use of that warning is for
rule devs.
Or is sa-update on trunk no longer feeding rule updates to 3.3.1 and
older versions so it truly is no longer an issue?
I will add this to my list o' rule gen questions as I believe we are
generating rules. And I'm sorry I read this poorly and now understand
the debug is so developers use if version loops.
Do people really care if the debug output is long?
