Custom Query (1030 matches)
Results (961 - 963 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #469 | fixed | source-note missing under certain conditions | ||
| Description |
compile a file containing a defgeneric as its last form, and load the compiled file. the source-notes for that function (and its methods) are missing, instead there are pathnames. Consequently slime fails when trying to "goto definition" (meta-.). Now for the magic: if you add some other definition (eg. a defun) below (and compile again), the source-notes are there!? example: (contents of file "~/source-note-test.lisp" ) (defgeneric adoctestfun (input)
;; (defun somethingunrelated (i) (* 2 i)) (compile-file "~/source-note-test.lisp") (load "~/source-note-test.dx64fsl") (find-definition-sources 'adoctestfun) -> no source notes ;; now uncomment the defun and try again: (compile-file "~/source-note-test.lisp") (load "~/source-note-test.dx64fsl") (find-definition-sources 'adoctestfun) -> ok, source notes are there (tested in 1.3-r11936 DarwinX8664 and 1.3-RC1-r11804MS (LinuxX8632) |
|||
| #450 | invalid | special keywords passed through process-run-function | ||
| Description |
Seen as cl-user> (ccl:process-run-function "Anon" (lambda (&rest args) (print args))
:use-standard-initial-bindings nil)
-| (:use-standard-initial-bindings nil)
It would be nice if these arguments were removed, or as the manual seems to imply, the args weren't passed through to function at all. |
|||
| #1001 | invalid | special operators without macro definition | ||
| Description |
The following special operators don't have a corresponding macro definition. ccl:nfunction ccl:compiler-let ccl::ppc-lap-function ccl::with-variable-c-frame ccl::with-c-frame ccl::fbind While the standard doesn't specify anything for special operators not in the CL package, it would still be nice if they followed the same rule as for CL macros implemented as special operators: 3.1.2.1.2.2 Macro Forms An implementation is free to implement any macro operator as a special operator, but only if an equivalent definition of the macro is also provided. since this would ensure that portable code walkers can be written. |
|||
