Well Boldra, you've thrown a proper little spanner into my works... I'm not complaining because I really like your example!

I was going to run a small number of regex conversions on an aXML string and turn it into classic XML to feed XML::Simple for turning into a perl structure, but I can't do that now if I want to use the method above. .o0(~Hrm~)

One quick question though, under this schema would every tag have to have a definition? As in what would happen to tags which are just markup around and within tags which have defined roles?

Also there is another thought that I don't know exactly how to describe I guess you could call it orphan data, for example:


listing actions/default/body.aXML
---------------------------------

<html>
  <head><title>acme products</title></head>
  <body>
    some orphan text that needs to be in the output
    <use>actions/<qd>action</qd>/main.aXML</use>
    some more orphan text
  </body>
</html>

[download]

I'm guessing that the above would be mapped to your moose solution thusly:


package actions::default::body;

my @nodes = (
 bless ( {
    'tag' => 'html',
    'data' => [ bless ( {
                  'tag' => 'head',
                 'data' =>  bless ( { 
                             'tag' => 'title',
                            'data' => 'acme products' }, 'Node' ),

                bless ( {
                  'tag' => 'body',
                 'data' => [ bless ( { 
                               'tag' => 'orphan',
                              'data' => 'some orphan text that needs t
+o be in the output' }, 'Node' ),
                            
                             bless ( { 
                               'tag' => 'use'
                              'data' => [ bless ( {
                                            'tag' => 'orphan',
                                           'data' => 'action/'}, 'Node
+' ),

                                          bless ( {
                                            'tag' => 'qd'
                                           'data' => 'action' }, 'Node
+' ),
 
                                          bless ( {
                                            'tag' => 'orphan',
                                           'data' => '/main.aXML' }, '
+Node' )
                                        ] }, 'Node' )

                             bless ( { 
                               'tag' => 'orphan',
                              'data' => 'some more orphan text'
                                   ), 'Node' )

                            ] }, 'Node' )
             ] }, 'Node' )
        );


sub getNodes { return @nodes; }

1;

[download]

In reply to Re^2: rough start of an axml compiler by Logicus
in thread rough start of an axml compiler 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.