Custom Query (1030 matches)

According to CLHS entry for Constant Variable LAMBDA-LIST-KEYWORDS, it is "a list of all the lambda list keywords used in the implementation, including the additional ones used only by macro definition forms".

(arglist #'+) on CCL returns (CCL::&LEXPR CCL::NUMBERS), which includes a keyword &LEXPR that is not on the LAMBDA-LIST-KEYWORDS list.

Therefore I conclude that CCL is not compliant when it comes to this issue.

This is a suggested patch to fix this behaviour.

​https://github.com/phoe/ccl/commit/5ac9d024c08fc5eb5302491be218143640aa3388

​https://github.com/Clozure/ccldoc/blob/master/source/toplevel.lisp#L40 This is where *nx-source-note-map* is declared to be a map, it is a dynamic binding.

​https://github.com/Clozure/ccldoc/blob/master/source/toplevel.lisp#L46 This is where the map is updated.

Is it just me, or is the hashtable not accessed anywhere else in CCLDOC and therefore wasted?

(There should be a CCLDOC component in here.)

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!