Altova Mailing List Archives


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

From: David Carlisle <davidc@--------->
To:
Date: 6/13/2005 12:09:00 PM
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.

would you also ban references to functions (or non-core functions) not
defined in the module? Something like that would appear to be needed if
you want to compile-time type-check expressions that involve function
calls.

In general whatrules would you envisage for all global name resolution;
both for references within the compiled stylesheets and for references
in the calling stylesheet to constructs defined in the compiled
stylesheet?

Wouldn't you need some analogue of import precedence for all kinds o
objects, templates, functions, variabes, etc?

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.