Hello Theo, Monday, November 21, 2005, 8:56:16 AM, you wrote:
TVD> On Sun, Nov 20, 2005 at 10:29:25PM -0800, Robert Menschel wrote: >> It only happens on SARE rules, and only on specific SARE files. >> Nobody within SARE can reproduce it. TVD> Really? I can reproduce this by putting in the single line: TVD> meta SARE_OBFU_OBLIGATION 0 >> This structure has worked well, until now. It fails as far as I know >> only on Richard's >>> i'm building SA r345765 on OSX 10.4.3 w/ gcc401 & perl 587. TVD> fails on my FC3 Linux machine and my OSX machine. Strange, then, that many others haven't reported the problem before. I've been using this construct since February. >> I cannot see any reason for these to fail on his system. Can anyone >> else find an explanation? TVD> meta statements aren't the same as if/then constructs? ;) Good enough explanation, though it doesn't explain why others who use the rules don't get the error. So we're back to the discussion had in January/February about the best way to avoid --lint errors when SARE rules are removed from *.cf files, but people have score lines for those rules. The goal is to not any any significant time, which means not adding any basic rules. I'm thinking that the best structure might be something like: meta SARE_OBFU_OBLIGATION TO_EMPTY && !TO_EMPTY which will always test false. Is there a better way to accomplish this? Bob Menschel
