Michael, So you are saying that rather than put the call in the VM itself, it would go in a plugin that does the right things for the various platforms? Is there a plugin per platform, or one that grows to cover them all??
How am I doing? If I'm at all close, it sounds like a winner. There are those who do not want too much reliance on FFI, and I see their point, um, to a point. The idea of being able to disable FFI from the command line is interesting from a security perspective, so a plugin seems a good way to go. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Rueger Sent: Saturday, March 07, 2009 11:46 PM To: [email protected] Subject: Re: [Pharo-project] last win32 VM Schwab,Wilhelm K wrote: > Torsten, > > It could be up to the VM if we made it that way. There is a function > call to get the system directory, and the VM can "just do that" vs. > the image needing to have access to FFI/Alien to do so. Perhaps the > other VMs could add something analogous, or just answer an empty > string, vm path, whatever if their hosts are better designed than > Windows (not that such a thing is imaginable... queue throat clearing > .wav). We could add that as part of the OSPlatform package and add a plugin returning platform specific "stuff". In Sophie we had packaged access to platform specific paths in an extra package using mostly FFI, but a plugin would be more sensible in the long run. Michael _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
