Regarding object query langugages, you might look at the CORBA system. As an object request broker, it needs to be fast, so the syntax is pretty simple. Of course, it may be too
low level, but will give you ideas.
With regard to parsing, I would first create a grammar. I find Parse::RecDescent too slow when speed is of the essence. Writing your own top-down parser should speed things up and for a small grammar, it should be be easy to maintain as well.
Top-down parsers are constructed from a grammar as follows:
- Each nonterminal in your grammar becomes a subroutine that you call
- Alternation '|' is handled with if-then statments
- Qunatifiers like '*' and '+' are handled with loops
- Nonterminal strings are matched using regexes.
For learning about parsing and translation, I recommend the dragon book: Compilers, by Aho, Sethi, and Ullman.
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||