On Wed, 2011-03-23 at 00:32 -0400, Daryl C. W. O'Shea wrote:
> On 23/03/2011 12:27 AM, Karsten Bräckelmann wrote:
> > Also, while this Perl bug is out there (which undoubtful will exists for
> > a long time on production machines), should we refrain from tflags
> > multiple body rules?
> >
> > Guess we cannot push them, unless guarded by a version 3.3.2 if-block.
>
> If that turns out to be what should be done, lint should be updated to
> catch when its not done so that it breaks the build and prevents the
> rules from ending up in an update to old versions.
Clearly, you are speaking about lint checking on our British Butler,
aren't you?
I mean, we cannot have old SA versions lint check for this. If we could,
we just could have fixed it instead. Which we cannot.
Though yeah, agreed, a lint check at least for Jenkins to catch
inappropriate tflags multiple for body rules and version <3.3.2 sounds
like a good precaution. Might back-fire, though, due to generated
scores. In the worst case, this is scorched earth until 3.4. :(
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
