Custom Query (1030 matches)
Results (895 - 897 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1076 | fixed | mailman archive line wrapping | ||
| Description |
Many/most/all archived mailing list messages have long lines. One example is http://clozure.com/pipermail/openmcl-devel/2009-December/010792.html The following two links suggest how this can be corrected. http://wiki.list.org/pages/viewpage.action?pageId=4030605 https://bugs.launchpad.net/mailman/+bug/266467 |
|||
| #1077 | fixed | *command-line-argument-list* is undocumented | ||
| Description |
The ccl-documentation.html does not mention *command-line-argument-list*. I believe it should. :) If you supply me with a specification of CCL command line argument handling, I offer writing the missing documentation myself. Cheers, max PS: Thanks for the great work on ccl! |
|||
| #1084 | fixed | deficient error reporting in flet on bad lambda-list | ||
| Description |
cl-user> (compile-file #P"~/test-flet.lisp")
#P"/home/pjb/test-flet.lx64fsl"
nil
nil
cl-user> (cat #P"~/test-flet.lisp")
(defun f (z)
(flet ((g (x) (list x x))
(u z))
(g z)))
; No value
cl-user>
The fact that the "lambda-list" for u is an atom should signal a program-error. CLHS flet says: lambda-list---a lambda list; for flet and labels, it is an ordinary lambda list; and CLHS 3.4.1 says: The syntax for ordinary lambda lists is as follows:
lambda-list::= (var*
[&optional {var | (var [init-form [supplied-p-parameter]])}*]
[&rest var]
[&key {var | ({var | (keyword-name var)} [init-form [supplied-p-parameter]])}* [&allow-other-keys]]
[&aux {var | (var [init-form])}*])
so lambda-list for flet and labels cannot be an atom. And in the case where I found this, u was also a global function, so perhaps this could be tested by the compiler to add a hint in the error message that perhaps the form was intented to be in the body of the flet. |
|||
