Re: [xsl] Re: [exslt] Re: [xsl] Importing compiled stylesheets

Subject: Re: [xsl] Re: [exslt] Re: [xsl] Importing compiled stylesheets
From: Barry Lay <blay@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 13 Jun 2005 19:20:09 -0400
Why not allow an implementation to include compiled stylesheets by recognizing something about them (like a header that is different from a regular text stylesheet)? That way the implementation could allow various levels of optimization from a full bytecode compile to some sort of tokenized form, and it wouldn't require a change to the spec. It does open the door to non-standard implementations, but perhaps that could be fixed in a subsequent specification. This would also mean that you wouldn't have to change the calling stylesheet, just the files it accesses.


Michael Kay wrote:

A compiled module will need to be defined as something more closed. It
may be a collection of many compiled stylesheets. What is important is
its property that it doesn't use/know about global objects that exist
outside this module (such as global variables, keys, etc). The only
way to pass information to this module is by using parameters.

And this affects the decision whether to add an attribute to xsl:include or
to use a new top-level element. If an attribute is added to xsl:include, the
semantics must be identical to xsl:include - loading the precompiled code is
then merely an optimization.

Michael Kay

Current Thread