The would be a slight improvement on what I have currently =), but most of my variability is having 10 different formats for say the log command so I still end up with a horrid list, maybe I can't escape that.

I'm expanding the interpreter to be a lot more featured so that it can process conditional things like...


if ( event >= other thing ) { do this; and maybe more things }

This makes the processing a bit more complicated so I guess I probably more curious as to how languages say perl, intepret language structure/grammar as I'm guessing they don't have some horrid long if loop

I suppose if I'm going to have say <25 permutations of commands only hardwiring the formats works, but making it reevaluate chunks in brackets as separate pieces starts to make life interesting and it would be nice to make it say the following...


if ( event1 > thing ) { data = var; goto func1 }
and if ( event1 > thing ) { goto func1; data = var; }

by just teaching it the formats... 

if () {}
data = var
goto func

[download]

rather than limiting the system to the permutations I'd hard coded. I guess this running a bit deeper that the original question i posted, appologies for not being more specific the first time.


Regards Paul

In reply to Re^2: command input processing by thekestrel
in thread command input processing by thekestrel

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.