Not that easy.
There are different categories of "bad practice" like unmaintainable code or dangerous code.
It's possible to built little regexes which run for years just b/c backtracking goes exponential in Perl but not in egrep.
So this depends on the engine used and involved optimization. (that much about "static analyzer for several languages")
At the same time the code you showed m/^.*blah.*$/ might be odd but not necessarily slower, cause
AFAIK will Perl first try to find the string "blah" somewhere, before continuing.
And it's NOT IDENTICAL to m/blah/ cause multilines wouldn't match w/o /s modifier.
DB<100> $str="\n blah \n"
DB<101> $str =~ /blah/
DB<102> $str =~ /^.*blah.*$/
DB<103> $str =~ /^.*blah.*$/s
So what's the recommended best practice here in your opinion?
Regarding analyzers, you might be interested in this recent discussion, which had pointers to different projects and older discussions:
Parsing and translating Perl Regexes
( addicted to the Perl Programming Language)
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||