I have been in your exact shoes, being the developer in a QA group. What we did was this:
  1. Create an event handler
  2. Each event is associated with a function (or some object/method pair ... your choice)
  3. The event handler chews through a list of pending events
  4. A given event can modify the list of pending events (so, LoadCommands would "Do The Right Thing")
  5. Create a starting event (like LoadCommands <filename>, or somesuch)

You might want to look at POE. We rolled our own, but that was almost 4 years ago, when POE was still in infancy. The other nice thing about doing event handlers is that simple scripting commands (SET, JZ, JNZ, etc) are very simple to implement. Once you have JZ and JNZ, you have (almost) all of your basic logic-flow (if, while, for, etc) implementable in those terms. (They're actually implemented in those terms in most ASM flavors.)

------
We are the carpenters and bricklayers of the Information Age.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re: Keyword parser function mapping module by dragonchild
in thread Keyword parser function mapping module by apprentice

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.