252
edits
Nasal Initialization: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
= Initialization of Nasal core-/default-modules = | = Initialization of Nasal core-/default-modules = | ||
When Flightgear starts, it will start the Nasal parser and load modules from FGDATA/Nasal. | When Flightgear starts, it will start the Nasal parser and load modules from FGDATA/Nasal. | ||
== Root directory / core modules == | == Root directory / core modules == | ||
| Line 17: | Line 17: | ||
'''Sub-sub-directories will not be scanned for .nas files - at least not automatically on FG startup.''' | '''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. | 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 / Disabling modules == | |||
There is a mechanism to enable/disable modules in the C++ domain (in FGNasalSys), however, at the time of writing, the state of this mechanism is unclear. This section shall be updated once the desired design as well as the implementation has been clarified. | |||
= Open questions = | = Open questions = | ||
Review the sources to confirm / update this doc. | Review the sources to confirm / update this doc. | ||