Hi
The man page for CLISP mentions that it can produce C code, but doesn't say
which command line option will do that. Does anyone know?
Thanks
Wroot
--
Please note: mail sent to ·····@my-deja.com is ignored.
On Sat, 15 Dec 2001 02:46:18 -0500, Wroot <·····@my-deja.com> wrote:
>The man page for CLISP mentions that it can produce C code, but doesn't say
>which command line option will do that. Does anyone know?
If nobody else answers then I say, though in win32 version which I'm
using, FFI doesn't work (yet?). You should read about FFI facility in
impnotes in FFI section.
AFAIK when you compile the file (with -c option) containing FFI calls,
the C file is automatically generated.
> * In message <················@news.vtc.ru>
> * On the subject of "Re: CLISP: producing C code"
> * Sent on Sun, 16 Dec 2001 11:47:59 GMT
> * Honorable ····@altavista.net (Arseny Slobodjuck) writes:
>
> in win32 version which I'm using, FFI doesn't work (yet?).
CLISP does support FFI on w32.
it does not (yet, pending libltdl integration) support dynamic modules.
--
Sam Steingold (http://www.podval.org/~sds)
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
Any programming language is at its best before it is implemented and used.
On 17 Dec 2001 16:23:00 -0500, Sam Steingold <···@gnu.org> wrote:
>> in win32 version which I'm using, FFI doesn't work (yet?).
>
>CLISP does support FFI on w32.
>it does not (yet, pending libltdl integration) support dynamic modules.
Then say please, how do I get a file 'clisp.h' in win32 ? (Actually I
built it, but I used some shamanic/arcane knowledge and still can't
use FFI).
> * In message <················@news.vtc.ru>
> * On the subject of "Re: CLISP: producing C code"
> * Sent on Tue, 18 Dec 2001 13:39:11 GMT
> * Honorable ····@altavista.net (Arseny Slobodjuck) writes:
>
> On 17 Dec 2001 16:23:00 -0500, Sam Steingold <···@gnu.org> wrote:
>
> >> in win32 version which I'm using, FFI doesn't work (yet?).
> >
> >CLISP does support FFI on w32.
> >it does not (yet, pending libltdl integration) support dynamic modules.
> Then say please, how do I get a file 'clisp.h' in win32 ? (Actually I
> built it, but I used some shamanic/arcane knowledge and still can't
> use FFI).
IIUC, clisp.h is needed for dynamic modules, which are not supported on
win32 (yet), so you do not need it to use the FFI.
please see <http://clisp.cons.org/impnotes.html#dffi>.
--
Sam Steingold (http://www.podval.org/~sds)
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
Takeoffs are optional. Landings are mandatory.
> * In message <············@newsmaster.cc.columbia.edu>
> * On the subject of "CLISP: producing C code"
> * Sent on Sat, 15 Dec 2001 02:46:18 -0500
> * Honorable Wroot <·····@my-deja.com> writes:
>
> The man page for CLISP mentions that it can produce C code,
where does it say that?
(I vaguely recall this too, and I want a specific reference as to what
part of the manual to fix).
> but doesn't say which command line option will do that.
it produces C files for the FFI forms only.
see <http://clisp.cons.org/impnotes.html#dffi>.
--
Sam Steingold (http://www.podval.org/~sds)
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
PI seconds is a nanocentury