Re: Design approaches to separating "pure" code from
How about a "pure" (your definition) module has no match patterns (input) and no literal result elements (output)?
It is useful to create modules that have no match patterns or literal result elements, especially for re-use. For example, generated text building or common calculations when doing publishing for multiple output formats. When you keep the literal result elements out of the common code, you can re-use the common code regardless of the result. Sounds obvious when written out, but I consciously will decide that a "common module" has only generated text and no literal result elements.
I hope this helps.
. . . . . . . . . . . . Ken
-- Contact us for world-wide XML consulting & instructor-led training Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Legal business disclaimers: http://www.CraneSoftwrights.com/legal
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format