|
920
|
1 <refentry id="runb">
|
|
|
2 <refnamediv>
|
|
|
3 <refname>RUNB</refname>
|
|
|
4 <refpurpose>BASIC09 run time package</refpurpose>
|
|
|
5 </refnamediv>
|
|
|
6
|
|
|
7 <refsynopsisdiv>
|
|
|
8 <cmdsynopsis>
|
|
|
9 <command>Runb</command>
|
|
|
10 <arg choice="plain">&replstart;i-code module&replend;</arg>
|
|
|
11 </cmdsynopsis>
|
|
|
12 </refsynopsisdiv>
|
|
|
13
|
|
|
14 <refsect1><title>Description</title>
|
|
|
15 <para>
|
|
|
16 BASIC09 run time package
|
|
|
17 </para>
|
|
|
18 <para>
|
|
|
19 Once one or more BASIC09 procedures are debugged to the programmer's
|
|
|
20 satisfaction, they can be "packed" or converted permanently to the
|
|
|
21 bytecode form.
|
|
|
22 </para>
|
|
|
23 <para>
|
|
|
24 Packed BASIC09 procedures are in fact OS-9 modules, and the OS-9 shell
|
|
|
25 recognizes them as I-code and passes them off to the virtual machine
|
|
|
26 emulator RunB for execution. RunB avoids a great deal of the overhead of
|
|
|
27 the typical interpreted BASICs of the day -- not to mention that one can do
|
|
|
28 integer calculations where appropriate rather than doing everything in
|
|
|
29 floating point -- so that BASIC09 programs run very quickly in comparison
|
|
|
30 with interpreted BASICs.
|
|
|
31 </para>
|
|
|
32 </refsect1>
|
|
|
33 </refentry>
|
