> > At the moment, there are two kinds of initialisation done for each
> > module:
>
> Both ELF and DLLs on Windows provide a way of specifying initializers.
>
> Or, easier yet, since the user is already using the hs_init function,
> you could use that. The way you'd do that in ELF is to define
> At the moment, there are two kinds of initialisation done for each
> module:
Both ELF and DLLs on Windows provide a way of specifying initializers.
Or, easier yet, since the user is already using the hs_init function,
you could use that. The way you'd do that in ELF is to define a
special se
> Hmmm, the garbage collector is a black box and has its own
> complicated heuristics for managing memory usage, but you are
> describing a mechanism that depends rather heavily on certain
> assumed behaviours. At the least, that gives the garbage collector
> less flexibility to change its own b
> > System.Mem.performGC does a major GC. When would a partial GC be
> > enough?
>
> I've described the image-processing example a bunch of times.
>
> We have an external resource (e.g., memory used to store images) which
> is somewhat abundant and cheap but not completely free (e.g.,
> eventua
> On 12-Aug-2002, Simon Marlow <[EMAIL PROTECTED]> wrote:
> >
> > I'd be equally happy (perhaps happier) if the header file spec was
> > removed altogether. In a sense, this would leave the
> Haskell part of a
> > foreign binding even more portable, because it doesn't have
> to specify
> > th
