Marco wrote:
Well for example for persons which develops in os linux (gcc) and not
microsoft who are developing in c for obtaining maximum performance
(and then they can't use JNI)....
Well, if you want to squeeze out every little bit of performance, you
should do it in assembler. But there is little proof that humans can do
it better. Same is true for C/C++ or whatever low level language you
want to use. Performance can be important, but I very much doubt that
porting a complex application like this from Java to C will benefit you.
And performance of XSLT has much more to do with how you design your
stylesheets than it has to do with the optimized opcodes.
If you really want to use C/C++, consider Eiffel. The Gestalt processor
is built in Eiffel and supports XSLT 2. Eiffel makes intermediary code
in C and optimizes that in several passes (called freezing I believe).
If you need performance, you need Eiffel. If you want C, use one of the
pre-final build phases from Gestalt.
Mind you, that XSLT 2 processors out-perform XSLT 1 processors on nearly
every respect, sometimes up to hundredths of times (and some gains are
even exponential), regardless of the platform.
-- Abel
--~------------------------------------------------------------------
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>
--~--