Re: CompileBL Scenario

Jason wrote:

> Isn't the compiler given the list to work from when it is loaded? 
Correct

Presumably the
> new places to look is just an extension of the "filesystem of the compiler" that
> it is told about when it is loaded anyway?

No, that was Marcel's point. The compiler previously looked in 2 of 
"its" directories and loaded any xsl stylesheets it found there: one for 
"BlockLayout language" tags (say xar:if) and the other for "Xaraya tags" 
(say xar:data).

With this addition it now checks for tags in any active module's 
modules/foo/tags directory. This means you don't have to move a module's 
tags when it installs into the compiler's directories. The price you pay 
is that the compiler has to know what modules are active and something 
about a module's directory structure, so that it knows where to look for 
tags.

So roughly speaking, to make the compiler standalone, we would need to 
remove this dependency. In doing so we would presumably then also be 
able to move the Xaraya tags mentioned above out of the compiler's area 
to somewhere else. There is one more sys::import call in the compiler 
that would also have to be changed. I guess that would about be it.

This is not a burning issue. I'm just interested in it for future 
reference and because any solution here might also be used in removing 
the remaining module calls from the core.

Marc