SDP

NAME
     sdp -- scripting definition processor

SYNOPSIS
     sdp -f {ast} [-i includefile] [-o directory | file | -] [-V version]
         [file]

DESCRIPTION
     sdp transforms a scripting definition (``sdef'') file, or standard input
     if none is specified, into a variety of other formats for use in building
     a scriptable application.  The options are as follows:

     -f format
           Specify the output format.  The format may be one or more of the
           following:

           a   Rez(1) input describing an `aete' resource.
           s   Cocoa Scripting ``.scriptSuite'' file.
           t   Cocoa Scripting ``.scriptTerminology'' file.

     -i includefile
           Include the type and class definitions from the specified sdef.
           Use this option to include a library of standard terms, e.g.,
           NSCoreSuite.sdef.  It may be repeated to specify multiple files.

           This option should be obsoleted by XInclude elements, but is not
           yet; see Bugs.

     -o directory | file | |Specify
           where to write the output.  There are three styles:

           directory     Write the output to automatically named files in that
                         directory.  Depending on the input and formats, sdp
                         may generate several files.

           file          Write all the output to that file.

           -             Write all the output to standard output.

           The default is `-o .'; i.e., generate files in the current directory.
           
           Because Cocoa Scripting requires each suite to be in a separate
           file, using -o file with -f s or -f t is usually not a good idea.

     -V version
           Specify the minimum system version to be compatible with. This flag
           is only meaningful for Cocoa Scripting (that is, -f s or -f t).
           Specifying ``10.3'' will generate NSString<FilePath> instead of
           NSString for type="file" attributes, and will disable warnings
           about non-object direct parameters.

SEE ALSO
     sdef(5)

BUGS
     sdp's error reporting leaves much to be desired.  It generally does not
     provide line numbers for errors, though it will describe the element.  It
     will not warn you of certain types of mistakes, such as using two different
     names with the same code (or vice versa), and will return a zero status
     even for erroneous input.

     sdp does not understand XInclude elements as described in sdef(5) and
     will simply ignore them.  You can continue to use the -i option to work
     around this.

Mac OS X                         June 6, 2002                         Mac OS X