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
use Perl Log In
lilstevey (4628)
lilstevey
(email not shown publicly)
Consumes:
(email not shown publicly)
Consumes:
- Heinekin
- Kro
- Addlestones
- Old Rosie
- Thatchers
- Strongbow
- Erdinger
- Guiness
- Budvar
- Leffe ( usually blond )
- Various Real Ales when in premises suitable
Friday April 28, 2006
05:27 AM
ant++ for code generation, only in perl.
I am contemplating writting a module ( or two ), and thought it wise to run my thoughts past a wider audience, on the very likley chance that I am stepping on familiar ground.
Basically I want to write a system of linking multiple stylesheets, and controlling the flow of xml documents between them, in order to generate code for different platforms from sets of source documents.
Kind of like Axkits xsl pipeline system, but more complex, and ( primarily ) for offline use.
I've already put a fair bit of thought into this, and preliminary investigations indicate that there isn't a great deal out there in this problem space.
I've seen the following projects which are java based, but still see merit in writting a perl variant, should one not already exist
Basically I want to write a system of linking multiple stylesheets, and controlling the flow of xml documents between them, in order to generate code for different platforms from sets of source documents.
Kind of like Axkits xsl pipeline system, but more complex, and ( primarily ) for offline use.
I've already put a fair bit of thought into this, and preliminary investigations indicate that there isn't a great deal out there in this problem space.
I've seen the following projects which are java based, but still see merit in writting a perl variant, should one not already exist
- http://www.langdale.com.au/styler/styler.html
- http://people.apache.org/~andyc/neko/doc/style/index.html
( personally to date I've used perl and XML::LibXSLT to generate them and see merit in formalising the common elements to shave off cruft ).
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Try the mailing list (Score:2)
It might be worth posting your question to the Perl-XML [activestate.com] mailing list. The traffic levels are fairly low but I know there are some XLST freaks hanging out there. :-)