Re: XSLT processing

From: Tod Harter <[email protected]>
> > Or get rid of
> > that messy, unreadable, undecipherable, undebuggable, everything-
> > looks-exactly-the-same, overly-talkative nonsense and do the job
> > using something sane.
> >
> 
> XSLT is the right tool for the job. Nobody makes you use it if you don't
> like it, but this list is here to help people with problems, not get on
> their case because they don't use your favorite tool. At least suggest
> something else if you know something better. Personally I have no problem
> reading XSLT and when its appropriate its orders of magnitude better than
> the alternatives.

It's heralded as the right tool for the job, yes. The hype around it 
is almost as big as the one there was around SOAP. The "Simple Object 
Access Protocol" that's everything but simple.

If I do not know what the original poster wants to do it's hard to 
suggest the best alternative.

Let's see, post something that's "orders of magnitude better than the 
alternatives" explaining what it does and we can compare our 
solutions.

Jenda
===== [email protected] === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed 
to get drunk and croon as much as they like.
	-- Terry Pratchett in Sourcery

_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs