Wed, 16 Aug 2000 08:06:59 -0700, Simon Marlow <[EMAIL PROTECTED]> pisze:

> This is a problem we've known about for a while, and it's one reason
> we have ForeignObj: because they're atomic heap objects and therefore
> don't suffer from transformational bogosity.

Oops. I think I understand now how ForeignObjs work.

So they have to stay. ForeignObj users can use the generic wrapper
    foreignObjToPtr :: (Ptr a -> IO b) -> ForeignObj -> IO b
instead of dedicated peek functions.

> PS. why are we talking in 10pt Arial?

No, we are talking in my own textmode 8x16 font.
With 128x48 characters on the screen.

-- 
 __("<  Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
 \__/
  ^^                      SYGNATURA ZASTĘPCZA
QRCZAK


Reply via email to