|laziness, impatience, and hubris|
>Youíve described a system that canít be stream parsed,
Yes it can, your just not smart enough to figure out how! having said that, stream parsing is a lame way of dealing with it.
>canít be readily consumed by available tools,
Sure it can, but there is no need for that.
>has an inflexible file-only input system,
LOL.. you can store the data anyway you want, I was specifying a ruleset, not a framework!
>will require running eval on raw Perl,
You might think that, but you would be wrong... Again! I'm guessing you haven't read Higher Order Perl by Mark Jason Dominus then?
>seems to have arbitrary grammar
Oh so arbitary, horror of horrors it adds just 2 extra characters to the existing standard. PHP has <?, TT has [% how arbitary is that?
>coupled with a highly limited priority system
ROFL!!! Highly limited is a description of your imagination, not the system I proposed.
>which will always be expensive to parse,
Are you rabid about parsing or something? Parsing is always expensive no matter what, and besides its very old fashioned, insert COBOL joke here.
>and brings nothing new to the game
That's what you think, my dear little living the past perl monk.
>that couldnít easily be done in TT or Mason or the Alloy family orÖ
It cannot be done in those or any other package I have found hence the reason I don't just use those packages... DUH!!!
>And they all have documents, community, examples, tests, profiling,
All of which takes time and effort I really can't be bothered to make. I have better things to do than to spoon feed you.
>and a really noticeable lack of ego about how effing Earth >shattering their approach to solving this well-trod problem >space is.
Cause and effect, showing humility here and lack of ego gets one response, going at it like a bull in a china shop gets an altogether more interesting (and useful) response.