Hello,
a first draft of my little Haskell-history collection is online now:
http://pseiko.gmxhome.de/pseiko/Haskell-History.html
Please note, that one part is still just copied from
http://www.idt.mdh.se/kurser/cd5100/ht02/history.html
but I hope it will evolve quickly. Moreover some parts are
hi,
Alastair Reid wrote:
Simon Peyton-Jones <[EMAIL PROTECTED]> writes:
Nothing deep. GHC is just a fairly big thing and one of its
assumptions is that it is compiling one module at a time. There'd
be quite a bit of chuffing around to remove this assumption.
Nothing fundamental, but real work.
> I am planning a Haskell project and I need to access files. Since the
> program will be automatically started whenever a mail comes
> in I will need
> to be able to lock the access to files. Is there any support
> for this in some library?
Yes, the Posix library distributed with GHC has suppor
Simon Peyton-Jones <[EMAIL PROTECTED]> writes:
> Nothing deep. GHC is just a fairly big thing and one of its
> assumptions is that it is compiling one module at a time. There'd
> be quite a bit of chuffing around to remove this assumption.
> Nothing fundamental, but real work.
The other big pro
On 17-Mar-2003 Simon Peyton-Jones wrote:
>
>| there is no need to use such hacks. it is not dificult to add suport
>| for mutually recursive modules to an implementation directly.
>| unfortunatley none of the working haskell implementations support
>| recursive modules,
>
> Simple in principl
I am planning a Haskell project and I need to access files. Since the
program will be automatically started whenever a mail comes in I will need
to be able to lock the access to files. Is there any support for this in
some library?
The second option that I have is to use a daemon and let the progr
| i am curious however, what is difficult about implementing recursive
| modules (that is, if it can be explained without getting into the
| technical details of GHC).
Nothing deep. GHC is just a fairly big thing and one of its assumptions
is
that it is compiling one module at a time. There'd
At 18:42 18/03/2003 -0800, [EMAIL PROTECTED] wrote:
> Example: I wish to define a structured container type, let's call it a
> "RatsNest", that is type-variable in two ways:
[...]
Do you consider the standard design lacking? For example,
I wasn't aware there was a standard design, but you have giv
