You say you've tried "everything possible", so just pick the one that gave you the correct solution. ;^)
Seriously, show the code that you've tried. I'm sure someone can (and probably will) just give you the answer, but it's more satisfying to help someone fix their code, rather than handing you the answer. Once you put up some code, someone will be sure to give you a hand finding out where you have difficulties.
I've recently played with YAPE::Regex::Explain, and if you try it out, you can tweak your regular expressions and have it tell you what it will do. That's a pretty good way to see where you're going wrong.
I'm assuming that you've already read perldoc perlre, so I won't bother mentioning it.
When your only tool is a hammer, all problems look like your thumb.
Update: Repaired CPAN link, thanks to toolic and atcroft for the catch!
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||