Since you are using the Tk::Text (or some inherited) API, it is simpler to encapsulate the text into logical tags, then parse contents in these tags differently according to tag type. This is the way VIM implements its syntax hilighting. It would be a lot nicer and powerful with Perl's regular expressions.
For example, given the code:
my $foo = "foo's $bar";
first, look for a string opening token (like qw/" ' qq. qr. q. qx./):
my $foo = "foo's $bar";
^
Then look for a corresponding close token (in this case /(?<[^\\])"/ to find the other end.
my $foo = "foo's $bar";
^---------->
Mark that part as a string. On a second pass, you might want to look for variables inside each string tag using $text->tagNextrange. (or the ones that evaluate "", qq//, etc)
At the end, you end up with something like the following (ignoring whitespace):
<perlcode>
<reserved>my</reserved>
<variable>$foo</variable>
<operator>=</operator>
<string>"foo's <variable>$bar</variable>"</string>;
</perlcode>
I hope you got the idea.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.