The OmniMark command-line options that can be used in OmniMark Studio for Eclipse are listed below. You can enter the command line options for your program in a launch configuration.
Many command line options have short forms.
You can combine several command line options into a file called an arguments file. You then name the arguments file on the command line using the -f command line option. The command line options in the arguments file will be read as if they had been entered on the command line. Arguments files are usually given the extension .xar.
Place command line arguments one per line, like this:
-include /opt/OmniMark/xin -log log.txt
To specify an arguments file that is to be read as part of the command line, use one of the following:
-argsfile testprogram.xar
-f testprogram.xar
To specify the directory where OmniMark should create temporary files when processing referents:
UNIX example: -temppfx
/usr/bin/omnimark/temp/
Windows example: -temppfx c:\omnimark\temp\
To specify a directory in which OmniMark should look for external function libraries (other than those specified in the global OmniMark options):
UNIX example: -xflpath
/usr/bin/omnimark/lib/=L.so
Windows example: -xflpath
c:\omnimark\lib\=L.dll
Short Form: -x /usr/bin/omnimark/lib/=L.so -x
c:\omnimark\lib\=L.dll
You must specify the file extension used for shared libraries on the platform OmniMark is running on. On UNIX, you must add the trailing slash and "=L.so". On Windows, you must add the trailing slash and "=L.dll". If the command line has more than one "-xflpath" option, OmniMark Studio for Eclipse will search those directories in the order you've specified them.
To specify a path to the include files (other than those specified in the global OmniMark options), use one of the following:
-i path
-include path
To force OmniMark to ignore include paths and external function library paths specified in environment variables and Windows registry entries (which is equivalent to checking the Ignore global properties box in the launch configuration):
-noenvarg
-noea
To specify a file to capture the data that OmniMark writes to standard output:
-of my-output.txt
To specify a file to which the data that OmniMark writes to standard output will be appended:
-aof my-output.txt
To attach a global stream to a file and have OmniMark write to that stream.
-os my-stream
my-output.txt
To attach a global stream to a file and have OmniMark write to that stream in append mode.
-aos my-stream
my-output.txt
You can set the initial values of global variables in the OmniMark script. Initial values set on the command line override those specified in the program source.
To set a switch variable to true, use one of the following:
-activate my-switch
-a my-switch
To set a switch variable to false, use one of the following:
-deactivate my-switch
-dea my-switch
To set the value of an integer variable, use one of the following:
-counter my-counter 44
-c my-counter 44
To set the value of a stream variable, use one of the following:
-define email-addr
"[email protected]"
-d email-addr "[email protected]"
To specify a file to which OmniMark will write log messages generated by the OmniMark script, specify one of the following:
-log testprogram.log (to
overwrite the existing log file)
-alog testprogram.log (to
append to the existing log file)
To add program execution statistics, including memory usage and execution times, to the log:
-stats
To display the version of OmniMark, specify:
-version
To display the authorization key for your OmniMark, or to view diagnostic information the the case of an authorization failure, specify:
-authkey
To suppress the message output at the end of program execution giving the number of reported markup error and warning messages:
-nocount
To suppresses the XML/SGML error number when XML/SGML error and warning messages are reported:
-noernum
To limit the number of XML/SGML error messages reported:
-limit 50 -threshold 20
To specify the name of a file containing OmniMark SGML/XML library declarations and comments to be used when resolving external text entities:
-library my-library.xlr
To specify a directory in which OmniMark should look for files specified in the system identifier portion of an OmniMark library declaration:
UNIX example: -libpath
/usr/bin/lib/
Windows example: -libpath
c:\lib\
Short Form: -l /usr/bin/lib/ -l c:\lib\
If the command line contains more than one "-libpath" option, OmniMark Studio for Eclipse will search those directories in the order they are specified. Note that you must include a trailing directory name separator ("/" on UNIX, "\" on Windows) at the end of the specified path, as the path is prepended to the name of the file when OmniMark Studio for Eclipse searches for it.
The OmniMark compiler produces warnings in the following categories:
ambiguity: A statement is potentially ambiguous. The compiler may not have interpreted the statement in the way you intended.
deprecated: The keyword you used is deprecated. You should use the modern equivalent.
dead-code: A section of code cannot be reached when your program is executed.
pattern: A pattern can match zero characters.
redundancy: The same declaration or modifier (or equivalent) is used more than once. OmniMark will ignore the duplicates.
uninitialized-data-access: A shelf isn't explicitly initialized or assigned any value anywhere, but its value is used.
By default, the OmniMark compiler will display all these classes of warnings except for uninitialized-data-access. You can change how each class of error is handled using the following command line options:
To promote the class of warnings to an error:
-warning-error warning-class
To ignore the class of warnings:
-warning-ignore warning-class
To report the error and continue compiling:
-warning-report warning-class
The -warning and -warnings command line options used in previous version of OmniMark no longer have any effect on the compiler.