I'm learning common LISP, and I wrote a simple program and interpreted it with clisp, worked, compiled it, worked, but i want an .exe, it just seems more official, and i don't want to go and get a commercial LISP implimentation, so how could I compile LISP code into a .exe with clisp?
i tried http://www.frank-buss.de/lisp/clisp.html and it didn't work, when i tried just "lisp" as the command, it told me i didn't have libreadline6.dll and when i tried clisp, it said the "lispinit.mem" wasn't created by clisp
Name:
Anonymous2010-10-03 15:57
also, while we're on the topic of my learning lisp, i want to have someone input a string, then the program takes that string and gets a float from it, how would one do this? (parse-integer "string") only works on integers, i know one could write this themselves, but i wanted to know if LISP had built-in support for this already before i started on that
>>6
I hadn't seen >>3. Fuck you, my post is hilarious.
Name:
Anonymous2010-10-03 18:22
>>1 i want an .exe, it just seems more official
There's a simple solution to your problem. Get over yourself. Alternatively, you could read your Lisp's documentation, which clearly spells out how to produce an executable, but we both know you'd rather complain than do any work yourself.
i want an .exe
You want Instant.EXE. It features the Instant.EXE Script Editor,
Instant.EXE Dialog Editor, Instant.EXE Menu Editor, 50 Powerful Commands and Over 200 System Variables!
Instant.EXE, because real men make their own tools.
Pretty much all implementations I've used support either compiling to executable/module or just dumping the memory image which can be used directly.
SBCL, ClozureCL, AllegroCL, LispWorks - native compilation, memory image (all data and code objects)
ECL - compile to C, which is natively compiled - your executables look the same as the usual C-compiled programs, tinier, but less fancy/real than memory image CLs.
There was also a fork of CLISP for generating bytecode and CLISP itself can be used to do that, but I've never deployed anything with GNU CLISP.
I prefer to develop everything in SBCL or CCL and deploy in SBCL, CCL or ECL. Switching implementations is very easy when using SLIME, but if you hate Emacs, you should try the commercial implementations, they're fine too.