Custom Query (1030 matches)

Trying to use nil as a function-name in defun crashes CCL 1.11. I think it should signal an error instead. I propose to change ccl::validate-function-name like so:

*** /usr/lib/ccl/level-0/l0-def.lisp
--- #<buffer l0-def.lisp>
***************
*** 118,124 ****
    name))
  
  (defun validate-function-name (name)
!   (if (symbolp name)
      name
      (if (setf-function-name-p name)
        (setf-function-name (cadr name))
--- 118,124 ----
    name))
  
  (defun validate-function-name (name)
!   (if (and (symbolp name) (not (null name)))
      name
      (if (setf-function-name-p name)
        (setf-function-name (cadr name))

I haven’t actually tested this (redefining validate-function-name on a running CCL leads to bootstrapping issues, don’t know how to avoid that).

When I launch wx86cl64 (version 1.11-r16635 (WindowsX8664)) I get the usual CL prompt, but when I (quit) the command line is not restored to a prompt (i.e. >). I can't input any other keyboard commands after exiting, it appears that the prompt is frozen.

I am running ccl on an Ubuntu 64 VM and I am having trouble getting lx86cl to run. This is a clean install of ubuntu with nothing installed on it but what comes with it by default, build-essential and subversion. I do not think the fact that I'm working on a virtual machine is causing the issue.

I followed the instructions to install ccl from ​https://ccl.clozure.com/install.html and the associated webpages. I used the command svn co http://svn.clozure.com/publicsvn/openmcl/release/1.11/linuxx86/ccl and this created the directory in /home/username/ccl.

I attempted to run ccl directly from the terminal using the command: ./lx86cl64 and this started the 64 bit ccl just fine. However using the command ./lx86cl returned bash: ./lx86cl: No such file or directory (same goes for trying to set up the ccl script in /usr/local/bin . ccl64 works fine, but not ccl). Which is strange because when I move to the ~/ccl directory the lx86cl binary is included in the folder.

What I haven't done:

• Attempted to try this on a 32 bit version of unbuntu
• Compiled from the source

In the past I just shrugged and moved on using ccl64 only, but now I am at a point where I need to test to make sure my project works in the 32bit version. So, I'm trying to make sure each works before I set up emacs, slime and quicklisp on this clean VM.

Any thoughts on getting the 32 bit version of CCL to work for this setup? Is this a true bug? Am I alone out here with this issue?

I'm not very experienced with linux so please let me know if I'm missing something obvious!