re : bracket escaping, my current implementation converts all the brackets in any data file it loads before beginning its processing... thats probably a slow way to do things but my code is improoving over time :)

re : the flow control thing, erm, i only mentioned the number of plugins to illustrate the example of the case statement was just one of many i could of made, many of the plugins could work equally well under any bracket type and thats why i chose to specify processing priority with the brackets rather than as someone said "making case always preceed its contents". I didnt intend to imply anything but that, and tbh most of the tags are nothing to do with flow control.. for instance



(notloggedin)
 
  (refas path="db/users/")users(/refas)  
     ##give access to the users dir through a <users> tag

  <trylogin username="<qd>username</qd>" password="<qd>password</qd>">
    <success>
       You are now logged in!
       Welcome <get ref="firstname">
                 <users><qd>username</qd>.xml</users>
               </get>
      [session add="username"]<qd>username</qd>[/session]
      [insertfile]securepage.xml[/insertfile]
    </success>
    <fail>
      <rem>go back to start and do not collect $200</rem>
      [insertfile]login_form.aXML[/insertfile]
    </fail>
  </trylogin>
(/notloggedin)

(loggedin)
 
  <insertfile>securepage.xml</insertfile>
 
(/loggedin)

[download]
note that within the brackets we could have it do multiple other things especially if we insert different files depending on the result. my current implementation of the insertfile calls for a parser restart, which allows for the file to contain another bunch of () < > and [ ] tag levels.

re : perl millions of modules not needing precedence altering... huh? im not sure im suggesting what it is you think im suggesting.. this schema is just for organising modules in an xml-like format, um... dunno mate.

In reply to Re^4: more bracket chaos by simonodell
in thread more bracket chaos by simonodell

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.