in reply to Re^5: Reliable way to detect base64 encoded strings
in thread Reliable way to detect base64 encoded strings

when I use it as you have it I get
Unmatched [ in regex; marked by <-- HERE in m/ ^ (?: [ <-- HERE A-Za-z0-9+/ at C:\aaa\aeh_pop.pl line 153.
I thought I was getting a problem with the regex...not the IF....but I didn't copy this in because i figured it was something I was doing. I see matched brackets... I tried to pull up into one line thinking the white space was giving issues...that didn't help. Thanks.

Replies are listed 'Best First'.
Re^7: Reliable way to detect base64 encoded strings
by ikegami (Patriarch) on Apr 17, 2010 at 04:23 UTC
    Oops, mine wasn't valid Perl either! I used an unescape "/" in the pattern. Two solutions: escape it, or change the delimiter. I corrected the original post.
      None of the above code works for me?? I have been trying different regex's to find Base64's on webpages and then decrypt them. The above code doesnt even look like perl..more like php?? Is it a cgi code or something because ive yet to see perl in that type of format?? I know very little cgi at the moment. Im making my way through all the perl modules now and trying them out in scripts

        None of the above code works for me??

        There's no reason it shouldn't. I suspect your error is elsewhere. Provide a minimal runnable example and tell us how it doesn't work.

        The above code doesnt even look like perl..more like php??

        Similarity is to be expected since PHP is based on Perl, but it doesn't look anything like PHP. The PHP equivalent of my

        m{...}
        would be
        preg_match('{...}', $_)

        (I don't actually know PHP. That's based on a quick search.)