c as in "curved"

Changing the specials from lower to uppercase would be quite easy, perhaps it would be better to support both? Or would that be confusing?

I'm going to add that sub escape in the parser right now as I think it will be a lot faster than how I'm currently doing it:

   $aXML =~ s@&lab;@\<@gs;
   $aXML =~ s@&rab;@\>@gs;
   $aXML =~ s@&lcb;@\(@gs;
   $aXML =~ s@&rcb;@\)@gs;
   $aXML =~ s@&lsb;@\[@gs;
   $aXML =~ s@&rsb;@\]@gs;

[download]

Oh, btw there is also another special and token which I haven't mentioned yet.


pseudocode
----------

$aXML =~ s@`@<backtick>@gs;

while ( commands remain unprocessed )
   {
    foreach match for <any_command>
       {
        substitute for <`any_command>
        set found_command boolean flag true
       }

    if (found_command)
      {
       while ( find match for <`command>data</command> ) 
            {
             process if (
                         no nested ` chars found             
                        )

            }
      }
   }

[download]

The reason for that is so that it forces the tags to be computed innermost to outermost, by negating the ` control char. Also the parser does not proceed to the lower priority tag types until all of the higher types have been processed.

File inclusions restart the parser so that they can have a complete new tag hierarchy within them, which can then include another hierarchy and so on recursively.

I suspect the backtick char (and tag) probably won't be needed at all by a proper compiler.

I also have some ideas about an editor for aXML, as far as I can tell it should be possible to run tags in isolation right inside the editor to see what they output.

So if we have a bit of aXML like


  <baz><qd>foo</qd></baz>

[download]

And we give the editor a query in like an address bar at the top;

?foo=bar

Then right clicking foo could run the plugin and return the result right there.


  <baz>bar</baz>

[download]

This would make debugging really easy and quick! If "bar" is not what your expecting to get from the tag then you know the problem is with the plugin. If "bar" is correct, then you can click on one tag outwards to execute that and see what it does... and so on interactively.

It would beat the hell out of having to swap between browser and editor windows constantly to see what is going on, and say a double right click could restore it back to its original state.

opening up an inc tag like that would load the appropriate file, ready for editing, then when you click back to close it again the editor can automatically save the secondary file for you. This way you can navigate and traverse complex structures and hierarchies without having to load, save and close files manually.

In reply to Re^5: Thanks to Ikegami, Chromatic & Corion by Logicus
in thread Thanks to Ikegami, Chromatic & Corion by Logicus

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.