Arthur Ralfs <[email protected]> writes:
| Gabriel Dos Reis wrote:
| > Arthur <[email protected]> writes:
| >
| > | Hi Gaby,
| > |
| > | To start on developing some new functions in src/lib/sockio-c.c and
| > | expose them through your FFI mechanism I first tried a hello world
| > | example. Copying what you had done for other socket functions I put
| > | a hello_world function in sockio-c.c, added a prototype to
| > | src/include/sockio.h, and imported it in src/interp/sys-os.boot as
| > | doHelloWorld.
| > |
| > | When I build OpenAxiom from scratch this works so I can type
| > | doHelloWorld(0)$Lisp at the command prompt successfully.
| >
| > Hi Arthur,
| >
| > Are you using GCL or SBCL?
|
| Gaby, thanks, I'm using GCL but I'll try it with SBCL, I didn't think of
| that. I actually have a build with SBCL sitting there.
Here are some subjective opinions:
* debugging with GCL can be painful, especially in experimental phase.
* my debugging with SBCL is so far unparalleled by any other free Lisp
system I have been using.
* SBCL's support for shared library means that you don't need to
modify src/sockio-c.c while you're still in experimental mode.
You can edit your local C files at will, build the shared libary
and load it with loadNativeModule$System, e.g.
loadNativeModule("mylib.so")$System
then use the Spad FFI interface, without having to modify
interp/sys-os.boot
In summary, you will just need to know C and Spad. :-)
-- Gaby
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
open-axiom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
