> The need for nullForeignPtr arises when a function expects
> a pointer to some data structure or a null pointer. In this case I cannot
> make the foreign import have the type (Maybe (ForeignPtr ()) since it's not
> accepted by the FFI.
I guess I've mostly used this trick with GreenCard whcih sup
On Mon, Jul 07, 2003 at 07:31:13PM +0100, Alastair Reid wrote:
>
> > the discussion on ForeignPtrs without finalizers didn't come to a
> > conclusion. I specifically need the nullForeignPtr which was easy enough
> > with the FFI of GHC 5.04:
> > [...]
> > do I have to create a dummy C function?
>
Axel Simon <[EMAIL PROTECTED]> wrote,
> the discussion on ForeignPtrs without finalizers didn't come to a
> conclusion. I specifically need the nullForeignPtr which was easy enough
> with the FFI of GHC 5.04:
>
> newForeignPtr nullPtr (return ())
The discussion came to a conclusion with
ne
> the discussion on ForeignPtrs without finalizers didn't come to a
> conclusion. I specifically need the nullForeignPtr which was easy enough
> with the FFI of GHC 5.04:
> [...]
> do I have to create a dummy C function?
Yes, create a dummy C function.
(Actually, you could use 'free' since it doe
Hi,
the discussion on ForeignPtrs without finalizers didn't come to a
conclusion. I specifically need the nullForeignPtr which was easy enough
with the FFI of GHC 5.04:
newForeignPtr nullPtr (return ())
Judging from the source code of GHC 6.0,
newForeignPtr nullPtr nullFunPtr
will lead to a
