Alright! I've implemented alternative parsing algorithm and it works sweat. So far I haven't had any bugs with it (not that I'm aware of ;-). I'm nearly done implementing two tags now: 'cfoutput' and 'cfif'. The parser recognizes them correctly and seems to be building a parse tree that is ready for 'execution' provided the actual tag handler classes are coded completely.
Certainly, realizing there's little fun without actually seeing bits and pieces of the code, I'm going to provided here (or my ftp) as soon as I'm finished polishing it. I might also provide little snippets of a larger code in form of a separate runnable perl script, but I've got to find the time ;).
To sum up, nesting problem seems to have been dealt with! ;D
|
"There is no system but GNU, and Linux is one of its kernels." -- Confession of Faith
|
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.