Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • First, a detail: XSL:FO is a page description language (think HTML+CSS, but more comprehensive, and with full support for page-based layouts and typography), it's not a transformation language. XSLT is the transformation language; it's supposed to be used to transform semantically-structured XML documents into presentation form (be it text, HTML, XSL:FO, or whatever).

    Second, syntax is almost never a problem: XSLT is a nice transformation language in spite of the rather awful syntax. If TGE can get a tree-

    • Thanks for the clarifications and explanations! I think I starting to understand TGE and PAST but there is still a long way for me to go.

  • In my project Plumhead, http://rakudo.org/parrot/index.cgi?plumhead [rakudo.org] I'm working on a side by side comparison of various parser and tree transformation approaches. The use case is an implementation of PHP on Parrot.

    Currently I have XSLT, TGE and Antlr3 tree transformations. So far Antlr3 is the most convienient for generating the syntax tree as I need it for Parrot.

    --
    /* Bernhard.Schmalhofer@gmx.de */