Instead of:
$query->{action} eq "post" ? ($allowed{msgid} = '^(\d+|new)$') && ($al +lowed{data} = '^(([^|+]*[^|]+.*\|){4}[^|+]*[^|]+.*)$'):1;
try this:
$query->{action} eq "post" ? %allowed = (msgid => '(^\d+|new)$' , data + => '^(([^|+]*[^|]+.*\|){4}[^|+]*[^|]+.*)$)', action => 'post|edit|d +elete|long|short' ):1;
and so on. That works for me, though there may be a better solution. Your message was cut off before you told us why you iterate over %allowed--if you don't need the value of action in the iteration, this can be made simpler. Also, consider doing something about your use of sort as a key--the -w flag doesn't like that, either.

In reply to RE: How to write a nice rule base? by adamsj
in thread How to write a nice rule base? by TGI

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.