Matthew Flatt 8bd5dbf7cc ffi/unsafe: change `cast' to avoid pitfalls for you ... The old `cast' didn't work right for a mismatch between a pointer GCableness and the source or target types, and it didn't work right for an GCable pointer with a non-zero offset. While those pitfalls were documented, the first of them definitely has been a source of bugs in code that I wrote. Also added `cpointer-gcable?'		2012-09-04 15:28:18 -06:00
..
examples	Modernize (& racketize) ffi/examples.	2012-07-27 10:31:26 -04:00
unsafe	ffi/com: fix reference counting	2012-09-01 09:48:35 -06:00
com-registry.rkt	add ffi/com', ffi/unsafe/com'	2012-01-10 18:35:32 -07:00
com.rkt	ffi/com: add missing export	2012-09-01 09:48:34 -06:00
cvector.rkt
file.rkt	further error message convention refinements	2012-06-22 09:47:59 +08:00
info.rkt
objc.rkt
unsafe.rkt	ffi/unsafe: change `cast' to avoid pitfalls for you	2012-09-04 15:28:18 -06:00
vector.rkt
winapi.rkt