- From: <bugzilla@jessica.w3.org>
- Date: Wed, 02 Mar 2016 15:54:57 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29453 --- Comment #5 from Michael Kay <mike@saxonica.com> --- In general if a declaration occurs in an imported module then it can always be overridden in an importing module. An xsl:import in an imported module imports declarations with different precedence from the same xsl:import appearing in an importing module, and similar rules apply to an xsl:include in an imported module. We don't want to handle the complexity of use-package bringing components in at anything other than the highest import precedence of the using package, because the rules just get too complicated. We could define it so that xsl:use-package creates components at the highest import precedence regardless where it appears, but (a) that would be inconsistent with the usual behaviour of xsl:import, and (b) it would reduce our flexibility to introduce refinements in the future. In the scenario you describe where hundreds of stylesheet use one common module, we would encourage you to turn that module into a package so that it can be separately compiled and reused. That's what packages are designed for. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 2 March 2016 15:55:01 UTC