Custom Query (1030 matches)

With normal compilation setting, CCL does not detect that the argument list supplied when invoking a function is invalid.

Under certain circumstances that I have not yet isolated, CCL creates the error message "Function call arguments don't match current definition of <function>" when it finds invalid arguments. This is better, but still very unspecific, and makes locating errors harder than one would wish for.

As in:

foo.lisp:
(defun foo (&key a) (declare (ignore a)))
(defun bar () (foo :b 2)) 

Compiled with CCL:

paracetamol 25_> ccl -n -e '(compile-file "/tmp/foo.lisp")' -e '(quit)'
paracetamol 26_> 

SBCL generates useful output:

paracetamol 26_> sbcl --no-userinit --eval '(compile-file "/tmp/foo.lisp")'  --e
val '(quit)'
This is SBCL 1.0.11, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.

; compiling file "/tmp/foo.lisp" (written 12 MAR 2008 11:50:55 AM):
; compiling (DEFUN FOO ...)
; compiling (DEFUN BAR ...)
; file: /tmp/foo.lisp
; in: DEFUN BAR
;     (FOO :B 2)
; 
; caught STYLE-WARNING:
;   :B is not a known argument keyword.
; 
; compilation unit finished
;   caught 1 STYLE-WARNING condition


; /tmp/foo.fasl written
; compilation finished in 0:00:00

as does cmucl (no suprise, but still)

netzhansa 5_> lisp -eval '(compile-file "/tmp/foo.lisp")' -eval '(quit)'

; Python version 1.1, VM version Intel x86 on 12 MAR 08 01:01:34 pm.
; Compiling: /tmp/foo.lisp 12 MAR 08 01:01:00 pm

; Converted FOO.
; Compiling DEFUN FOO: 

; 
; 
; File: /tmp/foo.lisp

; In: DEFUN BAR

;   (FOO :B 2)
; Warning: :B is not a known argument keyword.
; 
; Converted BAR.
; Compiling DEFUN BAR: 
; Byte Compiling Top-Level Form: 

; Compilation unit finished.
;   1 warning


; /tmp/foo.x86f written.
; Compilation finished in 0:00:01.
netzhansa 6_> 

As does CLISP:

paracetamol 29_> clisp -x '(compile-file "/tmp/foo.lisp")'
  i i i i i i i       ooooo    o        ooooooo   ooooo   ooooo
  I I I I I I I      8     8   8           8     8     o  8    8
  I  \ `+' /  I      8         8           8     8        8    8
   \  `-+-'  /       8         8           8      ooooo   8oooo
    `-__|__-'        8         8           8           8  8
        |            8     o   8           8     o     8  8
  ------+------       ooooo    8oooooo  ooo8ooo   ooooo   8

Welcome to GNU CLISP 2.44 (2008-02-02) <http://clisp.cons.org/>

Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
Copyright (c) Bruno Haible, Sam Steingold 1999-2000
Copyright (c) Sam Steingold, Bruno Haible 2001-2008

Type :h and hit Enter for context help.

;; Compiling file /tmp/foo.lisp ...
WARNING in BAR in line 2 :
keyword :B is not allowed for function FOO.
The only allowed keyword is :A.
[FOO was defined in line 1]
;; Wrote file /tmp/foo.fas
0 errors, 1 warning
#P"/tmp/foo.fas" ;
1 ;
1
Bye.
paracetamol 30_> 

Certainly not something very important:

deng-hhueb 445_$ cd /tmp/ deng-hhueb 446_$ mkdir junk deng-hhueb 447_$ cd junk deng-hhueb 448_$ rmdir /tmp/junk deng-hhueb 449_$ /usr/local/openmcl/working-0711-10188/lx86cl64 -n Unhandled exception 11 at 0x300040396dbc, context->regs at #x7fff22a29b58 ? for help [11239] OpenMCL kernel debugger: b [...] (#x00002AAAAB3D5688) #x0000300040E74B6C : #<Function DO-XP-PRINTING #x0000300040E748FF> + 621 (#x00002AAAAB3D5710) #x0000300040E75434 : #<Function (:INTERNAL DO-IT XP-PRINT) #x0000300040E753FF> + 53 (#x00002AAAAB3D5738) #x0000300040E75BCC : #<Function MAYBE-INITIATE-XP-PRINTING #x0000300040E7598F> + 573 (#x00002AAAAB3D57B8) #x0000300040AA4BBC : #<Function FORMAT #x0000300040AA450F> + 1709 (#x00002AAAAB3D5860) #x0000300040599DC4 : #<Function %BREAK-MESSAGE #x00003000405999CF> + 1013 (#x00002AAAAB3D5A18) #x000030004059BA84 : #<Function BREAK-LOOP-HANDLE-ERROR #x000030004059B86F> + 533 (#x00002AAAAB3D5A70) #x000030004064E294 : #<Function %ERROR #x000030004064E12F> + 357 (#x00002AAAAB3D5A98) #x000030004036D11C : #<Function STREAM-IS-CLOSED #x000030004036D0EF> + 45 (#x00002AAAAB3D5AB0) #x00003000403D27BC : #<Method-Function STREAM-WRITE-STRING (BASIC-CHARACTER-OUTPUT-STREAM T) #x00003000403D270F> + 173 (#x00002AAAAB3D5B10) #x0000300040E74B6C : #<Function DO-XP-PRINTING #x0000300040E748FF> + 621 (#x00002AAAAB3D5B98) #x0000300040E75434 : #<Function (:INTERNAL DO-IT XP-PRINT) #x0000300040E753FF> + 53 (#x00002AAAAB3D5BC0) #x0000300040E75BCC : #<Function MAYBE-INITIATE-XP-PRINTING #x0000300040E7598F> + 573 (#x00002AAAAB3D5C40) #x0000300040AA4BBC : #<Function FORMAT #x0000300040AA450F> + 1709 (#x00002AAAAB3D5CE8) #x0000300040599DC4 : #<Function %BREAK-MESSAGE #x00003000405999CF> + 1013 (#x00002AAAAB3D5EA0) #x000030004059BA84 : #<Function BREAK-LOOP-HANDLE-ERROR #x000030004059B86F> + 533 (#x00002AAAAB3D5EF8) #x000030004064E294 : #<Function %ERROR #x000030004064E12F> + 357 (#x00002AAAAB3D5F20) #x000030004040EB64 : #<Function (:INTERNAL TRY-GETTING-DIRNAME CURRENT-DIRECTORY-NAME) #x000030004040EAAF> + 181 (#x00002AAAAB3D5F50) #x000030004040ED2C : #<Function CURRENT-DIRECTORY-NAME #x000030004040ECBF> + 109 (#x00002AAAAB3D5F88) #x000030004043F354 : #<Function MAC-DEFAULT-DIRECTORY #x000030004043F32F> + 37 (#x00002AAAAB3D5FA0) #x000030004063EA64 : #<Function INIT-LOGICAL-DIRECTORIES #x000030004063EA3F> + 37 (#x00002AAAAB3D5FB0) #x0000300040E8A614 : #<Function RESTORE-LISP-POINTERS #x0000300040E8A53F> + 213

It seems to loop until the stack is exhausted because the error message can't be printed.

There seems to be currently 4 sources for CCL tarballs:

• The subversion repository: ​http://svn.clozure.com (which may or may not be retired one day now that CCL is also on Github).
• A HTTP source: ​http://ccl.clozure.com/ftp/pub/release.
• A FTP source: ​ftp://ftp.clozure.com/pub/release.
• Github release tarballs: ​https://github.com/Clozure/ccl/releases.

The first three sources do not provide encrypted transport which is a security issue. Github release tarballs are available over TLS, but the last stable version (1.11) is only available as source.

I just created a stable CCL package for Archlinux (​https://aur.archlinux.org/packages/ccl) which uses the FTP source, but it would be more secure to be able to switch to a source that supports TLS transport.

Providing binary tarballs (such as ccl-1.11-linuxx86.tar.gz) on Github would probably be the easiest solution for you, if you do not already have a SSL certificate for ccl.clozure.com. Additionally (or as an alternative), Let's Encrypt (​https://letsencrypt.org) could help you provide clozure.com in general over TLS.