[EMAIL PROTECTED] writes:
enabling types to express all properties you want is, IMO, the right way.
Why do I feel that there must be another approach to programming?
How many people do you expect to program in Haskell once you are done adding all
it takes to "express all imaginable properties
As far as SFRI 1 3 are concerned, this is all lifted from APL, so
you might just as well dust off an old APL manual and re-read it :)
-- O.L.
I would like to point out that on Solaris there are 2 SUN JDK releases:
so-called reference (put out by Javasoft) and production (by SunSoft). The
latter has had native threads for a while. Certainly they are here in 1.6 and
1.7. I don't know what is the situation on Windows, though.
-- O.L.
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
This thread and particularly the following passage:
"If I understand this right, you're suggesting essentially dumping
out part of the Haskell heap to a file."
reminds me very strongly of APL, where dumping the
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Tony Davie wrote:
This has well know disadvantages. Simon has already pointed out that
it's not relocatable.
How is it done in APL and in other systems that do it (SmallTalk
and some LISP systems, according to another
