-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Michael Kay schrieb:
| I think what you are missing is that in XSLT, imports have global effect.
| That is, if A imports B, then the things in B become visible to every
module
| in the stylesheet, not just to A; also things in A become visible to
B. So B
| doesn't need to import A.
My problem ist that there might be different contexts, in which the two
stylesheet-modules are used. So there might be a stylesheet C, using
some xsl:keys of A, without importing B, because it don't needs it
directly. Stylesheet D imports only B, because it uses no key of A.
In this case I would have to keep in mind, that they depend on each
other, so that importing one of them requires to import the other, too.
Or I have to guarantee that one of the stylesheets is never used without
the other, so that I can import the other in this stylesheet.
|
| I don't think there was a change here after the book was published -
either
| it's wrong, or you've misread it.
I must have misread this. You explicitly wrote that it is an error for a
module to import directly or indirectly itself.
wfg,
Jonny
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHxzY3GaEJacf6i/cRAoB+AJ4zg/L7c3OaC+zsbB054sAdHx9YSwCfTASr
X6zgLwPjAdEXSOPZokCYY2I=
=KnbJ
-----END PGP SIGNATURE-----
--~------------------------------------------------------------------
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>
--~--