Very briefly, all the functions in your example are typeless.
Not sure what you mean by typeless in this context?
The actual examples certainly have holes in them, it was just some very
late night doodling in response to you "how" question:-) But I'm not
sure that you ever _have_ to save data in xslt2 as element content do
you (which is I think where you are losing type information) unless you
need to serialise to an XML output. If you can hold the data in memory
as XPath sequences, you should be able to retain type information?
Oh do you mean you need to define separate functions for separate types
rather than rely, as I did, on the inbuilt polymorphism of the build in
F&O functions and operators? In that case yes you do need to get type
information but in that case it's not to do with the requirments of
partial function application, just getting round the limitation that
XPath2 signatures for user-functions have to be distinguished by arity
not type.
David
--~------------------------------------------------------------------
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>
--~--