ForeignPtr naming

Simon Marlow simonmar at microsoft.com
Wed Mar 26 05:03:01 EST 2003


> As Haskell finalizers need pre-emptive concurrency, maybe
> they should go somewhere related to concurrency.  Or we
> could have a "Foreign.Concurrent".

Ok, how about Foreign.Concurrent.newForeignPtr and
Foreign.Concurrent.addForeignPtrFinalizer?  i.e. dodging the naming
issue by using the module system.  It also means that code which uses
GHC's existing versions of these functions can be fixed by changing
imports only.

Cheers,
	Simon



More information about the FFI mailing list