What I'd be glad to have in the near future is the ability to pass to
the transformation extension objects, written in native .NET languages
like C#. AFAIK M.D.Peterson is working on this and I am confident he
will have good results soon.
The extension mechanisms in Saxon are now highly configurable: you can plug
in "extension binders" that implement their own rules for binding to
external functions, either alongside or instead of the default mechanism. So
it should be possible to do this in a very clean way.
I'm pleased to hear positive news about Saxon.NET from a demanding user.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--