G'day John,

Update: My apologies. I thought I'd read your post fully - I must be going blind. You clearly did explain why you wanted to do this. Ignore the crap I wrote. Sorry!

Perhaps if you explained why you wanted to do this, you'd get a better answer. However, to do what you describe, why not just negate the result of =~: 

$ perl -Mstrict -Mwarnings -E '
my $x = q{L,0010,8001149805,003,20121015,0600,267,204193,20121015,1300
+,,GBFER,204193};
my $y = q{L,0010,8001149805,003,20121015,0600,267,204193,20121015,1300
+,,XXXXX,204193};
if (! ($x =~ /(?:GBFER|GBFOO)/)) { say "match" } else { say "no match"
+ }
if (! ($y =~ /(?:GBFER|GBFOO)/)) { say "match" } else { say "no match"
+ }
'
no match
match

[download]

-- Ken

In reply to Re: Writing a negative regex using =~ by kcott
in thread Writing a negative regex using =~ by ftumsh

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.