Links: Next Previous Up Top
sgmlspl uses an event model rather than a procedural model -- instead of saying "do A then B then C" you say "whenever X happens, do A; whenever Y happens, do B; whenever Z happens, do C". In other words, while you design the code, sgmlspl decides when and how often to run it.
The specification file, which contains your instructions, is
regular perl5 code, and you can define packages and subroutines,
display information, read files, create variables, etc. For
processing the SGML document, however, sgmlspl exports a single
Links: Next Previous Up TopDavid Megginson <email@example.com>