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
|
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.
/Roger
|
Cart
