On the Cobol issue: Yes, I would rather do XML than Cobol :) I am hardly a XML guru, but I already like it more than Cobol. Technically, Code is data. Uniform data, since it is built up out of keywords and variables. A lex parser backend would ofcourse be handy, since you have to DO something with the code.
Two of many nice things about XML :

<DIR>
  • XML was designed to describe data.
    • </DIR> <DIR>
  • XML tags are not predefined in XML. You must define your own tags.
    • </DIR>

    Greetz
    Beatnik
    ... Quidquid perl dictum sit, altum viditur.

    In reply to Re: Re: Perl as XML by Beatnik
    in thread Perl as XML by Beatnik

    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.