Re: Separating and including library routines

["Stephen J. Tinney" <stinney@xxxxxxxxxxxxx>]

Just to followup on the recipe for including libraries, there is a
wrinkle to be aware of if you are defining element-handling
specifications in libraries.

If the main style-specification has a default entry, that has priority
over named element entries in a style-specification included via the
'use' method.

Thus, in my examples if tst.dsl contains:

-------
<!doctype style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN"[
<!ENTITY libsgml system cdata dsssl >
]>
<style-specification id=main use="sgml">

(default (empty-sosofo))

</style-specification>

<external-specification id=sgml document=libsgml >
-------

and libsgml.dsl contains:

---------
<!doctype style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN">

<style-specification id=sgml>

(declare-flow-object-class element
  "UNREGISTERED::James Clark//Flow Object Class::element")
(declare-flow-object-class formatting-instruction
  "UNREGISTERED::James Clark//Flow Object Class::formatting-instruction")

(define (newline)
  (make formatting-instruction data: "&#13;"))

(element TST 
  (make sequence 
	(process-children)
	(newline)))

</style-specification>
---------

The result of processing tst.sgm is no output.

 Steve

 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist