Within programs that are to be compiled, references to result sets (created by set-processing commands) require special care. References to result sets can create problems, because the order in which the Compiler processes a program could be different from the order of execution. Problems can be avoided by creating permanent result sets (set objects) in…
Read more
Most problems with references to named sets can be alleviated by adhering to the following guidelines: Qualify set operations by explicitly giving the set name where possible (e.g., next set1, top set1) rather than letting the software implicitly assume the current set. Declare set objects in the database, forcing the software to check the structure…
Read more
The Compiler works from top to bottom through a program, reading every command line and disregarding programming structures and the flow-of-control commands (such as IF&ldots;ENDIF, WHILE&ldots;ENDWHILE, BREAT, CONTINUE, RETURN, STOP, and BYE). During compilation, the software creates a result set for every set-processing command that implicitly or explicitly produces a result set. For example, compilation…
Read more
The examples that follow illustrate how result set references are compiled and indicate situations to be avoided. Example 1 procedure test() find all Employees -> EmpSet . . . other non-FIND commands . . . find all Departments -> DeptSet . . . other non-FIND commands . . .endprocedure This procedure contains two set-processing commands that create result…
Read more
In the context of compiled programs, the term permanent object refers to any object that, once created in the application database (based on a definition in the Object Dictionary), persists until erased. Permanent objects include EntitySets, relationships, roles, application documents, application directories, windows, menus, displays, forms, constants, variables, and permanent result sets (set objects). Application…
Read more
With a few exceptions, all Zim application programs can be compiled. Compiling one or more programs in an application carries several benefits, including security, speed of execution, and minimized resource use. This section discusses the compiler, prerequisites for compiling programs, adjustments to be made to application programs before compiling, and the commands used to compile…
Read more
A compiled program is called in the same manner as any other application program. For example, if you have compiled a procedure program called RunTest, call it as follows RunTest () Appropriate expressions would be entered within the parentheses (if required). If it is necessary to run a program disregarding its compilation, the command: SET…
Read more
The disk location of compiled programs is pertinent only if you are copying the application database to another location, managing disk space, or building a fully compiled application. Each compiled program is stored in a separate file with the same name as the source code file in a directory of the operating system that corresponds…
Read more
Once you have developed an application system, you have four alternative approaches to using it. You can choose not to compile any part of the application. You can compile the programs at any time during the development of your application. We recommend, however, that you test and debug all programs fully before compiling them, as…
Read more
The Zim Compiler is used to compile application programs. The Compiler reads the programs that you have written (source code) and produces object code. The compiled code is placed into a disk file separate from the disk file that contains the source code. The compiled version of an application program is semantically equivalent to the…
Read more
English 
Portuguese