On Sun, Dec 26, 2010 at 8:19 AM, Joachim Geidel <
[email protected]> wrote:
>
> Hi Eliot,
>
> On Nov 11, 2010; 02:40am, Eliot Miranda-2 wrote:
> > But I'm hoping that the ALien callouts will die the death soon. I have
> > Alien callbacks integrated with the FFI and of course the ALien data
> > manipulation code works fine. So if you're eager to have Alien callouts
> > work see whether the above change fixes things, in which case I can
> > integrate the fix. But if you're not so eager you could wait for me to
> > push out the FFI changes, but that could take a few weeks.
>
> What exactly does "Alien callouts will die" mean? Does it mean that the
> Alien class library is deprecated and will be replaced by a new version of
> FFI? Or is it something else?
>
It means what it says; that the callout primitives in Alien will die and all
the rest will remain. FFI callouts will accept Aliens and, because they
have type information, render the Alien call-outs redundant and problematic.
The Alien data representation and callback facilities will be retained.
>
> I am close to releasing JNIPort for Pharo/Squeak. I am currently using
> Alien
> for interfacing to the Java VM, and with the exception of callbacks from
> the
> JVM to Smalltalk which come from foreign threads, everything works now on
> the Squeak VM ("foreign" callbacks still crash the VM which outputs
> "scheduler could not find a runnable process" to the console).
>
> I would be a bit unhappy if I had to dump this work and redo the interface
> to the JVM, and I wouldn't be happy at all if I had to use different class
> libraries for calling foreign functions depending on the VM (Cog vs. Squeak
> VM). So, what's the "official" plan for Alien/FFI?
>
> Best regards,
> Joachim Geidel
> --
> View this message in context:
> http://forum.world.st/Alien-Cog-VM-tp3036626p3164309.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
>
