Subject: [xsl] 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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] [ANN] Balisage 2011 Program A, Tommie Usdin | Thread | Re: [xsl] Design approaches to sepa, David Carlisle |
RE: [xsl] distinct values by xslt, JS Rawat | Date | Re: [xsl] Design approaches to sepa, David Carlisle |
Month |