I'm just learning LISP just for fun. I downloaded and
installed CLISP 2.38, on windows xp. There are a
couple of points that makes life a little harder
(like there is no right-click menu to copy, paste,
etc.), but not a big deal. There is one thing though,
which I believe is a bug, or, say an oversight on your
Not being very fond of editing test on the command
prompt, I define some functions in a text file. Then
copy the definition, and paste it using the system
menu on the left upper corner of the console window.
Here what happens:
If my file is saved with \n line endings, and code
spans over multiple lines, everything works OK. But if
the file is saved as a usual windows text file (in
Notepad, say) I get strange errors. You could say
"well, then save it as a unix text file", but I use
the same method for a couple of different interpreters
to try my code, and if I do so, comment lines creates
a problem for them. this necessitates to maintain two
version of each file, headache...
To illustrate the problem, I attached a sample session
in a text file. Please note that #\[ is read L#[ by
interpreter, which is obviously a problem.
If I type it on the program window, it works.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Get latest updates about Open Source Projects, Conferences and News.