Dear all,
For the past couple of years, I have been quietly hacking on a brand new
version of QuickCheck with lots of cool features. I have been
distributing copies to some friends, but have not released any official
package.
Now, after lots of peer pressure, the time has come that I want to
rel
+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->+*->
DEADLINE-EXTENSION-DEADLINE-EXTENSION-DEADLINE-EXTENSION-DEADLINE-EXTENSION
Workshop on Mathematically Structured Functional Programming
http://cs.ioc.ee/mpc-amast06/msfp/
New deadlin
Hi,
Why not just call it, say, Test.QuickCheck2?
I think module names should reflect only their functionality. I don't
see how "External" or "Contrib" or "Chalmers" would say anything
useful about the functionality of the modules.
A while ago I sent a proposal for "package mounting", which I thi
In the recent discussion on "Haskell as a disruptive technology" I
predicted that MS would incorporate functional programming into its
languages.
See here for details.
http://lambda-the-ultimate.org/node/1406
Paul.
___
Haskell mailing list
Haskell@h
On Apr 11, 2006, at 11:18 AM, Paul Johnson wrote:
In the recent discussion on "Haskell as a disruptive technology" I
predicted that MS would incorporate functional programming into its
languages.
MS does this already, for quite some time. The product is called ...
Excel.
Any spreadsheet
