This section includes the following FlashBASIC modules
topics.
Creating a FlashBASIC module A BASIC module is a subroutine that does no I/O and is call from an external source. (It is possible to post-compile an object without the source.)
Cataloging a FlashBASIC Module Cataloging makes code easier to locate. It is not necessary to catalog a BASIC module to run or call it. Cataloging does not affect performance since the object code is always loaded in a dynamically extensible shared memory segment.
Running a FlashBASIC module Once compiled, the BASIC object code can be run directly, or it can be cataloged. This topic explains how to run a BASIC module.
Running FlashBASIC from a Windows command prompt BASIC object code can be exported to a DOS file with a .D3F extension, and then combined with a launcher to turn it into an executable that can be run directly from a Windows command prompt. It is also possible to configure Windows to recognize the .D3F extension as an executable and associate it with the Flash interpreter (see Notes below), which makes the Flash module significantly smaller.
Running FlashBASIC from Visual Basic When using a FlashBASIC module with the D3 Visual Basic class, D3clsRuleModule, some differences and constraints are applied due to the differences between the Windows and D3 environments.