ZBasic Language Reference
146
ZBasic Microcontrollers
file and vice versa. Argument files may contain blank lines and comment lines (beginning with a pound
sign or an apostrophe).
--array-base=<value>
This option specifies base for arrays that do not explicitly specify the lower bound. The specified value
must be either 0 or 1.
--call-functions[={on|off}]
This option can be used to control whether ZBasic functions may be invoked as if they were subroutines.
It is only permitted for native mode devices and then only for functions that return a fundamental type
(Byte, UnsignedInteger, String, etc.) The presence of this option affects only those ZBasic source files
processed after the option is encountered. It may be used multiple times if desired. Omitting the equal
sign and value has the effect of enabling the feature.
--called-by-list
When this option is specified a “called-by” list is appended to the map file. The called-by list will indicate,
for each subroutine or function, each routine that invokes it. This information may be useful in analyzing
the impact of changes in your code. If no map file is generated this option is ignored.
--calls-list
When this option is specified a “calls” list is appended to the map file. The calls list will indicate, for each
subroutine or function, each routine that it invokes. This information may be useful in analyzing the
impact of changes in your code. If no map file is generated this option is ignored.
--code-limit=<value>
This option requests that the compiler compare the size of the generated code with the specified limit
value. The limit value is specified in decimal, optionally using the suffix K or k to denote a multiple of
1024 bytes. If the code size exceeds the limit an error message will be generated. The default code limit
is 0, which value disables the code size checking.
--code-type=<code-type>
This option is used to request that the compiler generate a particular type of code. The set of acceptable
values for <code-type> depends on the type of the target device. For VM devices, the only acceptable
code type is zvm. For native target devices, either c (the default) or cpp may be specified. The latter
code type is useful if you want to include C++ code in your application.
Example
--code-type=cpp
--create-library[=<file>]
This option, useful only for native mode devices, requests that the compiler build an object code archive
(object library) instead of building an executable file. If the library filename is not specified, the library file
will have the name of the project file or the first module processed with the extension replaced by .a.
The compiler will also create an additional file containing ZBasic declarations for all of the public entities
in the library. The declarations file will have the same name as the library with the extension replaced by
.inc.
 |
 |
 |