Succeeds if all necessary components for the running programare available, and the user has specified --check. The check-options strategy must have been added to the command lineoptions of the running program, see check-options for details. Additionally, xtc-check-dependencies will only run if the userspecified --check on the command line when invoking the program.

Succeeds if the input term is a FILE

Succeeds if the input term is stdin, and it can be successfullycopied to a FILE.

Clean up temporary files and exit program. In normal operation,XT components create temporary files, which should be cleanedup on program exit. Calling this strategy instead of<tt>exit</tt> ensures that no files are left behind.

Searches for an XT component, by name. The input to thisstrategy is the name of the component, as registered inthe XTC registry. If found, a FILE representing its location (path) is returned.

Option parsing wrapper for XTC programs that only read data. Thisstrategy functions like xtc-io-wrap, except that it only exposesthe -i option, and will not write any output to pipe (or file).

Typically, s will start with a call to read-from.

Example: xtc-input-wrap(read-from ; id)

Option parsing wrapper for XTC programs that only read data. Thisstrategy functions like xtc-io-wrap, except that it only exposesthe -i option, and will not write any output to pipe (or file).

Typically, s will start with a call to read-from.

Example: xtc-input-wrap(ArgOption(....), read-from ; id)

Applies the strategy s to the current term, then writes the resultto output. The output file is taken from the -o option on the commandline, if given, or defaults to stdout, if not.

Option parsing wrapper for XTC programs that only generate data. This strategy functions like xtc-io-wrap, except that it onlyexposes the -o option, and will read any output from stdin(or file).

Typically, s will will end with a call to write-to.

Example: xtc-output-wrap(!"foo" ; write-to)

Option parsing wrapper for XTC programs that only generate data. This strategy functions like xtc-io-wrap, except that it onlyexposes the -o option, and will read any output from stdin(or file).

Typically, s will end with a call to write-to.

Example: xtc-output-wrap(!"foo" ; write-to)

Wrapper strategy that automatically cleans all temporary filescreated by s. This strategy is used to wrap a strategy <tt>s</tt>,which can create one or multiple temporary files. All temporaryfiles will be cleaned up automatically, and the result of<tt>s</tt> will be returned.

Writes a FILE to the output of this component. The outputis file is retrieved from the -o option given to theprogram; if -o was not given, stdout is used.

Copies one file to another. If the new file has the same nameas the old, no action is taken. In addition to a real file,the new file can be stdout (or stderr). In this case, the contentsof the old file will be written to stdout (or stderr) before thefile is removed.

Writes a (list of) string(s) to a temporary file. A singlestring, or a list of strings is written to a text file. Thefile name is generated automatically, and returned by thisstrategy.

Reads a term from a stdin. The input on stdin is assumed to bean ATerm. It will be parsed, and returned as a term.

Renames one file to another, on disk. If the new nameis identical to the old, no action is taken. The oldfile can also be 'renamed' to stdout, in which casethe content of the old file is written to stdoutbefore the file is removed.

Write a term to a temporary file, in binary. The name of the fileis generated automatically, the term is written to it in thebinary ATerm format (BAF), and a handle is returned by this strategy.

Write a term to a temporary file, as text. The name of the fileis generated automatically, the term is written to it in thetextual ATerm format (TAF), and a handle is returned by this strategy.