[Home] [By Thread] [By Date] [Recent Entries]

Subject: Re: Design approaches to separating "pure" code from "impure" code?
From: David Carlisle <davidc@xxxxxxxxx>
Date: Thu, 19 May 2011 14:51:38 +0100
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
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member