[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

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


Subject: Re: [xsl] Design approaches to separating "pure" code from "impure" code?
From: "Christopher R. Maden" <crism@xxxxxxxxx>
Date: Thu, 19 May 2011 12:34:43 -0400

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/19/2011 09:45 AM, Costello, Roger L. wrote:
> I define "pure" code as code that doesn't do any I/O.
>
> I define "impure" code as code that does I/O.

Yesterday, I wrote some pure code that calculates the largest prime
number.  It also figured out your Social Security number, and the exact
date of the Earthbs creation.

Unfortunately, as it did no input or output, it was either not very
useful, or identically useful to every other piece of pure code.

~Chris
- --
Chris Maden, text nerd  <URL: http://crism.maden.org/ >
Does this mean we can have our civil liberties back now?
GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3VRqIACgkQGfhmdwB3wxlOGgCg0nBWAaEYDrn0w9ZNrGoerg9M
ruwAn3lW80+GXZggoEiB+EU5ValCxXbP
=ziIP
-----END PGP SIGNATURE-----


Current Thread