I have a non trivial set of XSLT code in a library where I have ended up (quite understandly) with some cyclic and/or multiple includes of the same file.

So…

Warning at xsl:stylesheet on line 10 column 63 of value.xslt: SXWN9019 Stylesheet module file:.....value.xslt is included or imported more than once. This is permitted, but may lead to errors or unexpected behavior Error at xsl:function on line 59 column 54 of value.xslt: XTSE0770 Function value:getValue#1 is declared twice - see .../value.xslt#59 ....

I’ve only recently done this (to simplify the structure of the code) and, it breaks.

Having investigated this my understand that this is valid in some contexts (as the error message indicates), but doesn’t really work, (as the error message indicates)…which is a tad confusing, I assume there is some scenario where this does work, but I’m breaking the rules.

How do I do this? (this is common issue in other languages, I remember using #defines in .h files in C, and F#, for example, doesn’t allow cycles, but has quite sophisticated ways to wriggle around the issue).

(SaxonHE12-4Jsaxon-he-12.4.jar)