#2 Autoloadable map entries bind to package variables

[Kevin Rogers]

I think it may be a mistake in millscript for entries in an
autoloadable map to bind to variables in their parent
package.

e.g. consider the following autoloadable map, in the main
inventory of a website:

|-feature.map-+-sample.ms
| `-text.txt

MillScript would declare a variable called "feature" to be
autoloadable. After autoloading, you still have a variable
called "feature" which is autoloadable, a variable called
"feature" which is the result of autoloading the map and a
variable called "sample" where:

sample == feature["sample"]

I think this is a mistake as entries in an autoloadable map
directory are just keys in that map.

[Kevin Rogers]

Logged In: YES
user_id=934534

This is not a mistake as such. We actually need a new loader
for millscript expressions, e.g. files ending in ".ms.expr".

The standard ".ms" loader is a BindingLoader. e.g for a file
"sample.ms", the ".ms" loader expects something called
"sample" to have been declared after the file has been loaded.

The new ".ms.expr" loader would be a ExprLoader. e.g. for a
file called "sample.ms.expr", the ".ms.expr" loader would
expect to load a single expression(e.g. a FUN) which would
be stored as the value associated with the key.