| The FlightGear forum has a
subforum related to: Nasal Scripting
|Memory Management (GC)|
some notes on how Nasal files from FGDATA/Nasal are processed when Flightgear is started.
Initialization of Nasal core-/default-modules
When Flightgear starts, it will start the Nasal parser and load Nasal (.nas) files from FGDATA/Nasal.
The nasal root folder (FGDATA/Nasal/) is scanned for .nas files and these files are loaded in alphabetical order. After all .nas files are loaded /sim/signals/nasal-dir-initialized is set, which triggers listeners in some of the files just loaded. This allows to use functions from other core files, which have just been defined, e.g. which were not yet available when parsing the file.
|Note for a list of modules see Nasal Modules|
Nasal load priority (version 2020.1)
Since version 2020.1 files that are listed in /Nasal/loadpriority.xml will be loaded first (in the order they appear in this XML). The remaining files will be loaded in alphabetical order. After some dependency checks, loadpriority.xml was filled with the relevant filenames. Most of the listeners (nasal-dir-initialized) have been removed accordingly.
Optional (load-once) modules
After the files in the root directory have been processed, the first level of subdirectories is scanned for .nas files. Each subdirectory defines a module / namespace which becomes available only after the files in the subdirectory have been completly processed, e.g. a variable foo in module bar becomes available as bar.foo only after parsing of the respective folder.
Sub-sub-directories will not be scanned for .nas files - at least not automatically on FG startup. Of course, files of sub-sub-directories can be included (sooner or later) by the Nasal code that is being processed, so optional code can be loaded on demand.
Enabling of load-once modules
From the user (aircraft developer) point of view, enabling of this modules is done by setting the property /nasal/<moduleName>/enabled to true.
If a module is needed by an aircraft, you can just add the following to your aircraft-set.xml file (replace module_name by the name of the desired module):
<PropertyList> <nasal> <module_name> <enabled type="bool">true</enabled> </module_name> <nasal> </PropertyList>
Loading is done in the C++ code and is a little bit complicated (see FG sources /src/Scripting/NasalSys.cxx). FGNasalSys::init() scans FGDATA/Nasal for subdirectories and calls FGNasalSys::addModule() for each subdirectory passing its name as module name and a list of all .nas files in it.
FGNasalSys::addModule() in turn creates property nodes for each file like /nasal/<moduleName>/file[i] = <filename>
|Caution For each subdirectory there SHALL be an entry in FGDATA/defaults.xml defining the default state of the module.|
|Warning At the time of writing addModule() creates /nasal/<moduleName>/enabled and sets it to true if it was not defined in defaults.xml. This is about to be corrected.|
init() continues, sets the property /sim/signal/nasal-dir-initialized to true which will trigger listeners in some of the previously loaded Nasal files.
Next it calls FGNasalSys::loadPropertyScripts() which checks all the /nasal/<moduleName>/enabled nodes. If true, the files will be loaded by calling FGNasalSys::loadModule() which in turn calls FGNasalSys::createModule().
Otherwise, if enabled is false, a listener is added that will load the module when enabled is set to true.
|Note The module name (which defaults to the name of the subdirectory) is also the name of the Nasal namespace in which functions and variables will be created.
If the namespace already exists, the module will be added to it so you can extend existing modules. But be very careful when overloading existing modules, you can easily break things.
This type of module can be loaded and unloaded at runtime without exiting or restarting FlightGear. See Modules.nas for details.