On Mon, Aug 3, 2009 at 06:19, bryan
rasmussen<rasmussen(_dot_)bryan(_at_)gmail(_dot_)com> wrote:
How far would you say the PHP with extensions stack can go to handle
the functionality of XSLT 2.0 - minus XSD integration? What things are
absolutely missing?
Well, using the DOM library in PHP, there really is nothing that you
can't do that XSLT 2.0 can do, anything from regExp and grouping to
lots of stuff that xSLT 2.0 in itself can't (and shouldn't) do. I once
did an inverse XSLT framework where program-flow was done through XML
and XSLT, and program execution was extensions, and it works quite
fast, too, even though it may not be the best way to go about things.
:)
I suppose that even if the above is an easy task that doing something
like enforcing side-effects free usage of the extensions would be
basically impossible (especially given the aforementioned pragmatism
of php and that side-effects are allowed in extensions)
Well, you probably can't guarantee that, no, but with a bit of smart
OO in the PHP layer I'm sure you can write interfaces and taxonomies
that guarantee it through *those* classes. But I reckon it's smarter
to just go Saxon (even with that PHP <-> Java bridge) as it truly
kicks ass.
Regards,
Alex
--
Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps
--- http://shelter.nu/blog/ ----------------------------------------------
------------------ http://www.google.com/profiles/alexander.johannesen ---
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--