
-- The following directive will spawn a second copy of ocpp, which takes as
-- it's input the file "example.ocp" and writes output to "example.occ":

#SHELL ocpp example.ocp -o example.occ

-- "example.ocp" contains references to a template file, "example.otp", which
-- are used to automatically generate several IOSEQ buffer/multiplexor PROC
-- declarations with a variety of protocols and termination methods. It also
-- manipulates two special internal macros: OcppIrrevocable, to hide all
-- reserved comments (This has been done here for convenience only, see the
-- documentation for other options) and OcppInLineInsert, to ensure that a
-- single output file is created with no embedded #INCLUDE directives.

-- A header comment in "example.otp" details how to use it to control the
-- protocol used, whether a buffer or a multiplexor is generated and the
-- various methods by which the procedure can be made to terminate.

-- If you now examine "example.ocp", "example.otp" and "example.occ" you will
-- find instances of several of the more advanced ocpp directives mentioned
-- in the accompanying documentation. You may also wish to verify that
-- "example.occ" is acceptable to the occam compiler, and experiment
-- with the template to generate your own buffer/multiplexor flavours.
