Building An Individual File; Compiler Errors And Warnings; Compiler Error Types; Compiler Errors - AMX NetLinx Studio Instruction Manual

Building and Debugging Source Code
The currently active System is indicated in bold (in the Workspace tab of the
Workspace Bar). See the Designating the Active System section on page 29.
1.
Select Build Active System from the Build menu.


2.
The status and results of the build are displayed in the Status tab of the Output Bar.

Building an Individual File

You can select to compile a single Source Code, Include, or Module file, using the Compile, Compile As NetLinx and
Compile as Axcess commands (or toolbar buttons).
1.
Select the file that you want to compile:


2.
Select the appropriate compile command. There are several ways to access the compile commands - via the Build
menu, the System File context menus (in the Workspace tab of the Workspace Bar), the Editor window context
window, or via the toolbar buttons.




Any errors detected by the program before the build operation starts are listed in the
Pre-Build Errors dialog. This dialog gives you the option of ignoring the errors and
continuing with the build.
3.
The status and results of the build are displayed in the Status tab of the Output Bar.



Compiler Errors and Warnings

These help topics contain information on the various types of errors and bugs common to programming, and some
techniques for solving these problems. Note that Warnings will not automatically preclude a successful compile
operation. By contrast, Errors must be corrected before your program can be compiled.

Compiler Error Types

There are three general types of programming errors:




Compiler Errors

When the compiler finds an error during the compilation process, it informs the programmer. Most of the time these
errors occur due to a typographical error or incorrect syntax of a particular command. Unlike warnings, errors must be
corrected before your program can be executed. Compilation errors are described below:
106
Any errors detected by the program before the build operation starts are listed in the Pre-Build Errors dialog.
Assuming that a Master Source Code file has been defined for the System, this dialog gives you the option of
ignoring the errors and continuing with the build.
If the file is already included in the open Workspace, click to select the file and select the appropriate
Compile command from the Build menu.
If the file is not part of the open Workspace, open the file via the File > Open command, then right-click on
the file (in the Editor window).
If you create a new non-Project related file, without a Workspace file open, the Compile command compiles
the file using the compiler (NetLinx or Axcess) associated with the file when it was created.
If you open an existing non-Project related file, with a Workspace open, the Compile command compiles the
file using the compiler specified in the System communication settings for the currently active System.
The Compile as NetLinx command compiles the selected file using the NetLinx compiler.
The Compile as Axcess command compiles the selected file using the Axcess compiler.
See the Compiling Source Code Files section on page 45.
See the Compiling Module Files section on page 59.
Compilation errors - Errors that occur at compile time. The compiler alerts you to these errors immediately
and identifies each error and the line where it is located.
Run-time errors - Errors that occur after the program has been compiled and loaded into the Master
Controller. These errors are caused by program statements that attempt illegal operations.
Logic errors - Logic errors are errors in program design and thus are the programmer's responsibility; The
master cannot tell if the program it is executing is accomplishing what the user intends.
NetLinx Studio - Instruction Manual