...
Code Block | ||||
---|---|---|---|---|
| ||||
FUNCTION xpxCompileExpress_X (fileName : STRING;
diagnosticFile : STRING;
options : INTEGER;
VAR noOfWarnings : INTEGER;
VAR noOfErrors : INTEGER)
status : INTEGER;
|
This function runs one or more Express schemata through the EDMexpressXCompiler. Optionally it creates and populates an EXPRESS-X dictionary model in the EDMdatabase for of one or more of the compiled EXPRESS-X schemata. The EXPRESS
Arguments
...
Type | Name | Comment |
STRING | fileName | The Express-X schemata to be compiled |
...
. The fileName argument can specify more than one file by using wild cards |
...
(star) or by specifying several file names separated by the comma character. Any number of schemata can reside |
...
in one file. Short form schemata as well as long form schemata can be compiled. Short form schemata is schemata that contains interface (USE FROM , REFERENCE FROM) constructs. | ||
STRING | diagnosticFile | specifies the name of a file that will receive the error and warning messages from the EDMexpressXCompiler |
...
. If the diagnosticFile is an empty string or has the value indeterminate |
...
(question), then the output from the EDMexpressXCompiler |
...
will be to the EDMmodelConverter |
...
standard output window. |
...
INTEGER | options | See below; The options argument should be specified as a zero or as a sum of one or more integer constants. |
INTEGER | noOfWarnings | number of warnings detected during the compilation process. |
...
INTEGER | noOfErrors | number of errors detected during the compilation process. |
Return Value
...
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Options
...
Option | Comment |
STORING_SOURCE | Specifies that the Express schema(ta) in its original form will be stored in the EDMdatabase. This option is automatically enabled in the operation independent of being set in the <options> argument or not. Hence the original source schemata will always be stored in the EDMdatabase. |
DELETING_EXISTING_SCHEMAS | Specifies that the existing dictionary model(s) with the same name as the resulting dictionary model(s) from this compilation will be replaced by the new dictionary model(s) as long as there are no data models associated with this (these) existing dictionary model(s). Dictionary models with associated data models or associated Express-X dictionary models cannot be deleted before all the associated data models or associated Express-X dictionary models are deleted. |
PARSE_ONLY | Specifies that the Express-X schema(ta) will be checked for syntax errors only. No dictionary models will be created when this option is enabled. |
NO_DICTIONARY_MODEL | Specifies that no Express-X dictionary models will be created by this invocation of the EDMexpressXCompiler . |
CONTINUE_STORING_ON_ERROR | Enforces the EDMexpressXCompiler to create and populate Express-X dictionary model(s) of erroneous schema(ta). Only dictionary models of schema(s) compiled without any errors can be stored as an Express-X dictionary model(s) in the EDMdatabase when this option is unset. |
SDAI_WARNINGS | Activates EDMinterface/SDAI warnings relevant for the usage of EDMinterface functions on an instantiated data model of the actual schema. |
ERRORS_ONLY | Warnings will be suppressed. |
HTML_ERROR_LISTING | Specifies that compilation diagnostics will be written in HTML on files in the directory defined by the system variable EDMS_TMP_DIR. The diagnostic report is ready to be displayed by an Internet browser. There are three or four HTML diagnostic files with the following names:
The file named s_main.htm or s_main.html is the main file, hence this file should be specified to the actual Internet browser when displaying the diagnostic report. |
| Specifies that a report of map inheritance should be written to the EDMinterface current output device. This option is effective only when the MAP_INHERITANCE option is enabled. |
| The actual EDMcompiledrProject file will be copied as comment in the resulting long form file |
| The (full) file name of all source files and include files will be listed in the "actual order in the result file" as comment on the resulting long form file |
| The beginning and end of each source file and include file will be listed as comment in the resulting long form file |
| Line numbers of the long form file will be listed as comment |
| Line numbers of each source file and include file will be listed as comment |
Example
...
Code Block | ||
---|---|---|
| ||
<Missing Example> |
See also
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|