Difference between revisions of "IFDEF"
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
Line 12: | Line 12: | ||
==Syntax== | ==Syntax== | ||
#IFDEF <constant> | #IFDEF <constant> | ||
+ | |||
[<statements1>] | [<statements1>] | ||
+ | |||
[#ELSE] | [#ELSE] | ||
+ | |||
[<statements2>] | [<statements2>] | ||
+ | |||
#ENDIF | #ENDIF | ||
Revision as of 14:19, 17 March 2009
Contents
#IFDEF…#ENDIF
Class
Applications
Purpose
Compiler directives to allow inclusion or exclusion of source code based on a compile-time constant
Syntax
#IFDEF <constant>
[<statements1>]
[#ELSE]
[<statements2>]
#ENDIF
See Also
COMPILE, DEFINE, DO, DO CASE, IF, SET COMPILE, SET DEVELOPMENT
Description
The #IFDEF compiler directive can be used to allow inclusion or exclusion of source code based on the existence of a compile-time constant. The constant, <constant>, is defined using the #DEFINE directive. At compile time, the compiler checks if the <constant> is defined. If it is defined, the <statements1> that follow are included in the compiled program file. The <statements1> can be any valid Recital 4GL commands. If the <constant> is not defined, the <statements1> are excluded. If the <constant> is not defined and there is a #ELSE directive specified, the <statements2> following the #ELSE directive are included in the compiled program file.
This directive can only be used in compiled programs.
Example
#DEFINE RECITAL 1 #IFDEF RECITAL set compatible to recital set filetype to recital #ELSE set compatible to vfp set filetype to vfp #ENDIF
Products
Recital Database Server, Recital Mirage Server, Recital Terminal Developer