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
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--