Camm Maguire <c...@maguirefamily.org> writes:
[...] | You're probably already familiar with the legacy FFI using defentry, as | I think axiom uses this already. This is a bit slow, but functional. | | I've designed a new one with the goal of accessing shared libraries from | within GCL given its unique (it appears) ability to unexec a running | image, and reexec later, possibly on a different machine. A shared | library link therefore needs to be remembered in the image, together | with all code pointer locations which must be reset on image startup. | The following is implemented in the 2.7.0 tree, but can be backported | rather easily if you need it. Hi Camm, for OpenAxiom, GCL-2.6.8pre is the most reliable of GCL releases (and gcl-2.7.0 is still in "beta" version) so we use defentry. We would definitely welcome the ability to use shared libraries (as we do with other lisps such as SBCL, ECL, CLISP, or Clozure CL). Best, -- Gaby ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ open-axiom-devel mailing list open-axiom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
