A darcs pull today of CFFI leaves foreign-funcall unexpandable in SBCL.
; caught ERROR: ; (during macroexpansion of (FOREIGN-FUNCALL ... ...)) ; A function with declared result type NIL returned: ; CFFI::TRANSLATE-OBJECTS
Apparently this error message results from a function redefinition http://www.lispworks.com/documentation/HyperSpec/Body/03_bbc.htm
"A call within a file to a named function that is defined in the same file refers to that function, unless that function has been declared notinline. The consequences are unspecified if functions are redefined individually at run time or multiply defined in the same file."
See discussion http://meme.b9.com/cview.html?utime=3351855600&channel=lisp&start=33...
Liam
"Liam M. Healy" lnp@healy.washington.dc.us writes:
A darcs pull today of CFFI leaves foreign-funcall unexpandable in SBCL.
; caught ERROR: ; (during macroexpansion of (FOREIGN-FUNCALL ... ...)) ; A function with declared result type NIL returned: ; CFFI::TRANSLATE-OBJECTS
Apparently this error message results from a function redefinition http://www.lispworks.com/documentation/HyperSpec/Body/03_bbc.htm
Hmm, I can't figure out where such a redefinition might be happening nor can I reproduce this problem.
See discussion http://meme.b9.com/cview.html?utime=3351855600&channel=lisp&start=33...
[quoting some of your discussion in random order]
<LiamH> I know little about darcs; is it possible to go back in time? Then I might be able to figure out what patch caused the error to come up.
Well, should this turn out to be a CFFI bug, it's my fault. TRANSLATE-OBJECTS used to be a macro, I turned it into a function.
http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=annotate_shade... http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=filediff;h=200...
<LiamH> So somewhere in the macro expansion, CFFI is redefining TRANSLATE-OBJECTS.
I can't see where this could be happening. And wouldn't SBCL warn about this?
<LiamH> I do have a rather elderly version of SBCL <LiamH> 0.9.7.25
I suggest trying a more recent version of SBCL.
I wrote:
<LiamH> I do have a rather elderly version of SBCL <LiamH> 0.9.7.25
I suggest trying a more recent version of SBCL.
For the record, Liam reports that a more recent version SBCL does not show this problem.
-
Liam M. Healy -
Luís Oliveira