[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: 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
This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|