Loaders can be used to dynamicly load Neko primitives stored in NDLL libraries.
Loaders can be used to dynamicly load other Neko modules (.n bytecode files). Modules are referenced by names. To lookup the corresponding bytecode file, the default loader first look in its cache, then eventually adds the .n extension to the name and lookup the bytecode in its path.
Loaders can be used for sandbox security. When a Module is loaded with a given Loader, this loader can manager the module security by filtering which primitives can be loaded by this module or by rewrapping them at loading-time with custom securized versions. Loaders are inherited in loaded submodules.
getPath
path
field. It's a
linked list of Neko strings that is a parsed version of the NEKOPATH
.
This path is used to lookup for modules and libraries.
loader
is defined, this will be
this Module loader, else this loader will be inherited. When loaded this
way, the module is directly executed.
library@method
.
The primitive might not be used directly in haXe since some of the Neko values
needs an object wrapper in haXe.