[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A definition file should have the extension `.def', and is a freely formatted file consisting of numbers, strings, comments, keywords, and various punctuation.
A definition file consists of several clauses, which generally have syntax like the following:
clause-kind { specific-data... } |
For example, here is a complete definition file for a (hypothetical) fairly large non-beamable application:
application { "Dr McCoy" DAFp copy-prevention } /* This app has three code resources: code #1 with all unannotated functions, #2 with functions placed in the "editfns" section, and #3 with "viewfns" functions. */ multiple code { editfns viewfns } |
NOTE: some details of definition file syntax are subject to change as
we figure out just what ought to be in a definition file. For example,
it's unclear what the best way to handle filenames is: whether they
should appear in the file at all, or whether, for example, hack traps
should match corresponding filenames on the build-prc
command line.