On Thu, Aug 18, 2011 at 2:08 PM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
On Aug 18, 2011, at 10:51 PM, Eliot Miranda wrote:
On Thu, Aug 18, 2011 at 11:30 AM, Stéphane Ducasse <
stephane.ducasse@inria.fr> wrote:
Thanks eliot
BTW what is the future of alien compared to FFI. I'm still confused.
I've answered this many times before. Alien is fine for data representation and callbacks, but not for callouts (too simpleminded, works only on x86). But I have integrated Alien with FFI and will not be developing Alien callouts. Use FFI callouts instead.
But is FFI not good for representation and callbacks? My point is why having two systems each with a weak point (if FFI has weak points). I'm probably too stupid to understand so I will discuss with the guys here because I'm missing something.
They are now integrated (to a usable extent). One can pass Aliens through the FFI. So to use callbacks with the FFI one creates Alien callbacks and passes them as arguments through FFI calls. Simple.
Stef
Stef (finished to paint house - well nearly finished before running to
ESUG).
On Aug 18, 2011, at 7:37 PM, Eliot Miranda wrote:
Hi All,
I've just published Alien-eem.14 to
http://www.squeaksource.com/Alien. This fix needs to be integrated into each dialect's version of Alien. The bug causes VM crashes due to trying to free stale pointers from previous runs.
Alien-eem.14 Author: eem Time: 18 August 2011, 10:34:20.024 am UUID: 39bedad1-6159-4ba4-be35-277df2a25977 Ancestors: Alien-eem.13
Fix startUp: discarding of stale values from Alien's GCMallocedAliens
class var.
-- best, Eliot
-- best, Eliot
-- best, Eliot