Navigation bar
  Start Previous page
 119 of 156 
Next page End 114 115 116 117 118 119 120 121 122 123 124  

113
--verbose
This option, useful only for native mode devices, causes the output from the final build process to be sent
to stderr.  In the absence of this option, the output from the build process is captured in a file named
build.log created in the temporary directory.  (Use the –-keep-files option to prevent the build log
from being deleted after the build is complete.)
--version
This option causes the version number of the compiler to be sent to stdout.  The compiler will then exit.
--warn=<warning-type>[,<warning-type>...]
This option enables or disables specific types of warnings.  The warning types are described in the table
below.  To disable a warning type, add the prefix no- to the warning type, e.g. no-unused-param.  All
warnings may be disabled en masse using –-warn=no-warnings.
Warning Type
Number
Description
array-bounds
9
Warn about constant indices on arrays being outside of the valid range.
calltask-byref
1
Warn about invoking a task that uses ByRef parameters.
case-overlap
10
Warn about the same value appearing in more than one case
expression  or range in a Select Case statement.
data-range
3
Warn about data values exceeding the capacity for the specified type.
for-loop-termination
11
Warn about a For loop that may not terminate properly.
hidden-data
5
Warn about data definitions hiding definitions at outer levels.
never-returns
8
Warn that a routine will never return (automatically suppressed for the
entry routine and routines invoked using CallTask).
questionable-code
4
Warn about questionable coding practices.
structure-compare
12
Warn about comparison of structures containing allocated strings.
task-stack-size
13
Warn about insufficient task stack size.
undefined-var
2
Warn about the use of a variable before a value is assigned to it or
when at least one path through a function does not set the return value.
unused-param
6
Warn about an unused parameter.
useless-code
7
Warn about code that will never be executed or has no effect.
warnings
1000
Refers to all warning types collectively.
The invocation option –-help-warning displays similar information and also indicates which warning
types are on by default.
-D<id>[=<value>]
value is specified, the identifier is considered to be an integral identifier and is assigned the value 1.  The
value may be specified as a decimal value or, when prefixed by &H or 0, as a hexadecimal value. 
Otherwise, the value is considered to be a string value.  The string value may optionally be enclosed in
matching quote marks or apostrophes but this is only necessary if the value contains white space or
begins with a character sequence that would otherwise indicate that an integral value is being specified.
Note that depending on your operating system, using the ampersand or other special characters on the
command line may require special quoting or escape characters. 
If the identifier already exists, an error message will be displayed.  The –U option may be used to avoid
this situation.  Also note that identifiers defined in this fashion are also available to be used in program
code somewhat as if they were defined by a Const definition.  The primary difference is that integral
valued identifiers have a universal type that can be used just like a literal integral value.
Previous page Top Next page