The following options control the general processing of source files.

-n

Do not execute any command, but display each command that normally would be executed.

-v

Display each command before it is executed by .

-C

Stop processing after generating C code from the Zinc source modules.

-S

Stop processing after generating assembler code from the Zinc and C source files.

-c

Compile and assemble the source file but do not link.

-o file

Place the output in a file named file . Since only one output file can be specified, it does not make sense to use -o when compiling more than one input file unless you are producing an executable file as output. If -o is not specified, the default is to put an executable file in a.out , the object file for source Ns .suffix in source Ns .o its assembler file in source Ns .s , and its C file in source Ns .c .

The names of Zinc source files must end with .curry or .lcurry . The latter are taken to contain literate Zinc source and are deliterated first. All Zinc source files are compiled into C code. In addition, for every source file file Ns .curry and file Ns .lcurry , respectively, the compiler creates a file file Ns .icurry containing the module's interface. The compiler uses module interfaces when processing import declarations in a source module. In order for the compiler to find the interfaces of imported modules, the name of the source file should agree with its module name. Hierarchical module names of the form A.B.C are mapped onto the filesystem as in Java, i.e., the compiler expects to find the interface of this module in file C.icurry in directory A/B relative to the directory where the compiler was invoked or to one of the directories specifying the import search path.

The following options control the compilation of Zinc source into C code.

-g

Prepare the compiled code for executing the program with the declarative debugger. Note that code compiled with this option is incompatible with code compiled without this option. This option must therefore be used consistently for compiling and linking all modules of a program.

--debug

Synonym for -g .

--trusted

This flag has an effect only in conjunction with one of previous options. It tells that debugger that it can trust all functions from a module compiled with this flag. The debugger will not ask questions about such functions.

-i dir

Add directory dir to the list of paths used to locate interface files. By default, the compiler searches for interface files in the current directory and in its standard library directory ${exec_prefix}/lib/curry .

-H size

Change the heap size used by the compiler to size . It is possible to use the abbreviations size Ns k and size Ns M to specify the heap size in kBytes and MBytes, respectively. Note that this option does not effect the heap size of the compiled executable. Use -h size for this (see below).

The following list describes only the most common options understood by when compiling C source either directly or as a result of previously compiling Zinc source into C code. In fact, passes on most of its options to the C compiler. For a detailed description of these options see the gcc() man page.

-D name

Predefine name as a macro, with definition 1 .

-D name=defn

Predefine name as a macro with definition defn .

-U name

Cancel any previous definition of name , either built in or provided with a -D definition.

-I dir

Add directory dir to the list of paths used to locate header files. The standard library directory ( ${exec_prefix}/lib/curry ) is always included in this list.

-O

equivalent to -O1 .

-O Ns level

Controls optimization of the compiled code. -O0 disables all optimizations. Note that -O3 and higher levels will fail to produce valid code for Zinc modules on many architectures.

--ccopt opt

Passes the option opt to the C compiler without interpretation. For instance, in order to include debugging symbols in the compiled C code, invoke the compiler with --ccopt -g .

The following options are relevant while linking a program. The compiler creates a tiny C code file in this phase, which contains the startup code initializing the Zinc runtime system and starting the evaluation of the goal. This file is compiled like other C code during the link phase.

-g

Compile a program that invokes the declarative debugger. All Zinc modules must have been compiled with the -g option as well.

--debug

Synonym for -g .

-h size

Use size bytes for the heap of the Zinc program. Note that actually twice as much memory is allocated for the heap because the runtime system uses a two-space copying collector. The abbreviations size Ns k and size Ns M can be used for specifying the size in kBytes and MBytes, respectively. The default is to use a 4 MByte heap.

-k size

Use size bytes for the stack of the Zinc program. The abbreviations size Ns k and size Ns M can be used for specifying the size in kBytes and MBytes, respectively. The default is to use a 512 kByte stack.

-t size

Use size bytes for the trail stack of the Zinc program. The abbreviations size Ns k and size Ns M can be used for specifying the size in kBytes and MBytes, respectively. The default is to use a 512 kByte trail stack.

-p

Print cumulated execution times and memory usage statistics at the end of the run. If specified more than once, also print memory statistics at each garbage collection.

-e goal

Evaluate goal instead of main.main . The goal is evaluated with respect to the Zinc module that occurs last on the command line, the module specified with the -M option, or the Zinc prelude otherwise.

-T goal

Compute the type of goal . The goal Ns No 's type is computed with respect to the Zinc module that occurs last on the command line, the module specified with the -M option, or the Zinc prelude otherwise.

-M module

An explicit goal specified with the -e option is evaluated with respect to the module module if no other Zinc module occurs on the command line. module is either the name of the source file (ending in .lcurry or .curry ) or the name of a module whose source can be located in the current directory.

-L dir

Add directory dir to the list of paths used to locate libraries specified with -l options. The standard library directory ${exec_prefix}/lib/curry is always included in this list.

-l lib

Search the library named lib when linking.

--ldopt opt

Passes the option opt to the C compiler without interpretation. In contrast to --ccopt (see above), opt is used only during the link phase.

The operation of a Zinc program depends on the type of the goal being evaluated. If it is of type IO t , the I/O action described by the goal is executed. All command line arguments except for the runtime system options (see below) are available to the program and can be accessed with the function System.getArgs .

If the goal's type is not IO t , the program computes and prints the solutions of the goal with a depth first search strategy. A solution comprises the normal form of the goal and the bindings and constraints for its free variables. When run on an interactive terminal, solutions are presented one by one giving the user a chance to stop the computation after each solution. Otherwise, all solutions of the goal are computed.

This behavior can be changed by passing one of the options -i and -n to the program. If invoked with -i , the program computes the solutions incrementally as if it were run on an interactive terminal. If invoked with -n , the goal's solutions are computed all at once.

All Zinc programs run with fixed size heap, stack, and trail. Their sizes can be specified at link time, but can be changed at run-time by passing options to the Zinc runtime system. Such options must be enclosed with +RTS and -RTS arguments on the command line. The -RTS switch may be omitted if it is the last argument on the command line.

The Zinc runtime system understands the following options:

-b Ns mode

Use buffer mode mode for the standard input and output of the program where the following mode Ns No s are recognized

n

Unbuffered

l

Line buffered

f n

Fully buffered

The optional number n allows specifying the buffer size when using fully buffered mode.

-h n

Use n bytes for the heap in this run of the program. Note that actually twice as much memory is allocated for the heap because the runtime system uses a two-space copying collector. The abbreviations n Ns k and n Ns M can be used for specifying the size in kBytes and MBytes, respectively.

-k n

Use n bytes for the stack in this run of the program. The abbreviations n Ns k and n Ns M can be used for specifying the size in kBytes and MBytes, respectively.

-t n

Use n bytes for the trail stack in this run of the program. The abbreviations n Ns k and n Ns M can be used for specifying the size in kBytes and MBytes, respectively.

-p

Print cumulated execution times and memory usage statistics at the end of the run. If specified more than once, also print memory statistics at each garbage collection.

-d

Turn on the low-level tracer of the abstract machine. In general you do not want to see its output, but it may give hints to why a program does not compute an expected solution or runs into a deadlock. Beware that tracing can slow down program execution considerably and the output may be excessively large.