I dont know that I agree with this. I suppose you may want to walk the parse tree in other circumstances, but I dont see why simple printing out the exact code that failed would be insufficient, and I think that would be reasonably doable with what we have already. Sure, it may not work on some far out there cases, but then again I wonder what the use of such an insane assertion would be. Anyway, im not knocking the idea if it comes along, but until its here im not going to spend much time in anticipation. As I said IMO, %99.99 of the things that most macro langauges do can be done as well or better by perl itself. All that a defined macro language does is provide consistancy. Which in of itself is probably a good thing (or maybe a bad thing if you read my other node), but my original point was merely that a LFSP need not have macros within it.
<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||