Just an (almost) meta comment: Trying to do something like this with a single regexp is when you may start getting into "Now you have two problems" territory. As has been shown you can do this in one pass with deep regex engine magic, but were I to do it I'd instead break it down into a simple state machine and parse things line-by-line that way instead. And were the "language" being handled much more complicated then I'd look to use a proper parser module (Parse::RecDescent, maybe Marpa::R2) and let that write the state machine. If/when things change about the "language" I just would need to update the higher level grammar description instead of manually monkeying in more states.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.