Search results
Jump to navigation
Jump to search
- ...testable on their own, then those modules are likely to be importing other modules, in what can rapidly become a tangle of imports that leads to several probl ...ed from anywhere. Import this with <c>import</c>, but then load all other modules with the <c>ensureImport</c> function it provides. For example, if the abo4 KB (613 words) - 15:32, 17 February 2025
- ...ottom of any module in '''/sys/lib'''; when loaded and run directly, these modules run unit tests or otherwise do something useful.820 bytes (133 words) - 15:23, 3 June 2020
- | '''lib''' || a folder of utility modules intended for use with [[import]]950 bytes (151 words) - 01:30, 30 January 2025
- == Using a Sprite and No Import Modules ==4 KB (708 words) - 14:43, 30 August 2024
- Many of the modules in <c>/sys/lib</c> run unit tests. The <c>runUnitTests</c> function define1 KB (185 words) - 13:37, 29 October 2022
- [[Category:Sys Modules]]1 KB (185 words) - 02:06, 31 January 2025
- In this hypothetical example, a program two [[import]] modules, <c>gui</c> and <c>events</c>, encounters a error in the <c>gui</c> module1 KB (222 words) - 03:34, 4 January 2023
- Like all the modules in <c>/sys/lib</c>, the best documentation for the json module is the sourc2 KB (252 words) - 17:41, 12 September 2021
- Like all the modules in <c>/sys/lib</c>, the best documentation for mapUtil is the source code (2 KB (394 words) - 03:31, 16 October 2023
- | importPaths || [[list]] of directories searched for [[import]] modules3 KB (459 words) - 08:12, 18 February 2024
- Like all the modules in <c>/sys/lib</c>, the best documentation for stringUtil is the source cod3 KB (469 words) - 21:36, 26 August 2021
- Like all the modules in <c>/sys/lib</c>, the best documentation for listUtil is the source code4 KB (616 words) - 13:58, 12 February 2025
- Like all the modules in <c>/sys/lib</c>, the best documentation for mathUtil is the source code4 KB (583 words) - 22:32, 26 August 2021