[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Design approaches to separating "pure" code from "impu

Subject: Design approaches to separating "pure" code from "impure" code?
From: "Costello, Roger L." <costello@xxxxxxxxx>
Date: Thu, 19 May 2011 09:45:41 -0400
 Design approaches to separating "pure" code from "impu
Hi Folks,

This is a general design question.

First, let me define some terms:

I define "pure" code as code that doesn't do any I/O.

I define "impure" code as code that does I/O.

(Dimitre could probably provide better definitions of those terms)

I am seeking your suggestions on ways to organize XSLT code to keep pure code
and impure code separate.


Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.