The _init file
If a Lasso 9 compiled LassoApp contains an _init.lasso file at the directory root, it will execute the contents of the file on first load of the LassoApp. This means that any types or methods required can be loaded, and any other checks for dependancies can be made before the LassoApp is called from within LEAP™.
A more detailed explanation of _init.lasso and LassoApps in general can be found at http://lassosoft.wiki.zoho.com/Web-Apps-Lasso-Apps.html
An example autoloader for methods required by a plugin:
/* ==================================
Pull in known core methods
================================== */
local(coremethods = array(
'method1',
'method2'
)
)
with i in #coremethods do => {
lassoapp_include('/mylassoapp/methods/'+#i+'.lasso')
}
It is important to note that types and methods should include a process for determining if they already exist.
It is also worthy to note that Lasso 9 will load definitions and keep them resident in memory or cache until server restart, hence the need to load either at LassoApp initialization or as a dynamic library.