H98 FFI Addendum 1.0, Release Candidate 10

Simon Marlow simonmar at microsoft.com
Fri May 23 04:29:41 EDT 2003


I've been meaning to write up an addendum on Concurrency for a while,
but haven't got around to it.  That's not to say I hold a lock on it; if
anyone else wishes to tackle it then by all means go ahead, and I'll try
to help out where possible.

Cheers,
	Simon

> -----Original Message-----
> From: ffi-admin at haskell.org [mailto:ffi-admin at haskell.org] On 
> Behalf Of Simon Peyton-Jones
> Sent: 23 May 2003 08:42
> To: chak at cse.unsw.edu.au; ffi at haskell.org
> Subject: RE: H98 FFI Addendum 1.0, Release Candidate 10
> 
> The bound-threads story interacts with the FFI -- indeed, it's in a
> document in Haskell-report/ffi/threads.tex.  Do we ultimately plan to
> fold it into the FFI spec (but, awkwardly, it must speak of
> concurrency)? Or do we ultimately plan to have a separate "blessed
> appendix" on concurrency generally?  And if the latter, who would like
> to edit it?  Manuel has done a great job with the FFI spec; I doubt
> concurrency will be half as hard.
> 
> Simon
> 
> | -----Original Message-----
> | From: haskell-admin at haskell.org 
> [mailto:haskell-admin at haskell.org] On
> Behalf Of Manuel M T
> | Chakravarty
> | Sent: 22 May 2003 22:33
> | To: haskell at haskell.org
> | Subject: ANN: H98 FFI Addendum 1.0, Release Candidate 10
> | 
> | Dear Haskell Folks,
> | 
> | Release Candidate 10 of the H98 FFI Addendum 1.0 is now
> | available from
> | 
> |   http://www.cse.unsw.edu.au/~chak/haskell/ffi/
> | 
> | The change log since RC 7, which was the last version
> | circulated via haskell at haskell.org, is appended below.
> | 
> | Please review this specification carefully.  If no
> | suggestion that leads to a serious change is made within two
> | weeks, I will freeze version 1.0.
> | 
> | Thanks,
> | Manuel
> | 
> | -=-
> | 
> | Changes since RC9:
> | * 1:     Mentioning interaction with foreign threads as an open
> problem.
> | * 2 & 3: Removed `threadsafe' again, as the proposal for thread
> support is
> |          still evolving and it is not yet clear whether a new safety
> level
> |          is required.
> | * 5.5:   Added the type synonym `FinalizerPtr' and rewrite the
> documentation
> |          of finalizers.
> | * 5.6:   Clarified the description of `StablePtr'
> | * 5.8:   Added `finalizerFree'
> | * 6.2:   All the types in CTypes must be newtypes that are exported
> |          abstractly.
> | 
> | Changes since RC8:
> | * 5.8: `MarshallAlloc.reallocBytes' is no longer permitted on memory
> |        allocated with `alloca' or `allocaBytes'.
> | * 6.1: Deinitialisation of the RTS via `hs_exit()' followed by
> |        (re)initialisation with `hs_init()' must be supported.
> | 
> | Changes since RC7:
> | * Clarified the lexis of C identifiers and C header file names
> | * In `ForeignPtr', added `mallocForeignPtrArray' and
> `mallocForeignPtrArray0'
> | * Clarified spec of allocations functions adding constraints taken
> from the
> |   corresponding C routines
> | * `mallocBytes' and `allocaBytes' must align memory sufficiently for
> any
> |   basic foreign type that fits into the allocated block
> | * Removed typos in the description of the module `ForeignPtr'
> | * Added Peter Gammie to the list of acknowledged people
> | * `addForeignPtrFinalizer' guarantees that finalizers for a single
> foreign
> |   pointer are executed in the opposite order as they were added.
> | * `Storable': Require that the size is divisible by the alignment
> | * Added Ross Paterson to the list of acknowledged people
> | * Added hs_free_fun_ptr() and hs_free_stable_ptr()
> | * Changed order of arguments of `mkIOError' and `annotateIOError' to
> match
> |   with the current implementation in GHC's FFI libraries.
> | _______________________________________________
> | Haskell mailing list
> | Haskell at haskell.org
> | http://www.haskell.org/mailman/listinfo/haskell
> 
> 
> _______________________________________________
> FFI mailing list
> FFI at haskell.org
> http://www.haskell.org/mailman/listinfo/ffi
> 
> 



More information about the FFI mailing list