Re: [xsl] Design approaches to separating "pure" code from

On 19/05/2011 14:45, Costello, Roger L. wrote:

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

why that (highly idiosyncratic) definition? If you mean to keep separate purely declarative, side effect free functional code from imperative code then there are other things to consider besides I/O. (Extension functions for example.)

David


________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________

Current Thread
[xsl] Design approaches to separating "pure" code from "impure" code? Costello, Roger L. - 19 May 2011 13:45:58 -0000 David Carlisle - 19 May 2011 13:52:00 -0000 <= Message not available G. Ken Holman - 19 May 2011 13:54:10 -0000 Christopher R. Maden - 19 May 2011 16:35:12 -0000 Costello, Roger L. - 21 May 2011 19:33:24 -0000 Dimitre Novatchev - 21 May 2011 23:57:28 -0000

<- Previous	Index	Next ->
[xsl] Design approaches to separati, Costello, Roger L.	Thread	Re: [xsl] Design approaches to sepa, G. Ken Holman
[xsl] Design approaches to separati, Costello, Roger L.	Date	Re: [xsl] Design approaches to sepa, G. Ken Holman
	Month

<-prev [Thread] next->	<-prev [Date] next->
Month Index \| List Home

Re: [xsl] Design approaches to separating "pure" code from "impure" code?