March 2006 - cffi-devel - mailman3.common-lisp.net

[cffi-devel] %expand-type-to-foreign-dyn vs *runtime-translator-form*
by Stephen Compall 31 Mar '06

31 Mar '06

I was looking at the new type translator expansion interface and noticed that one would experience different behavior depending on method definitions. I'll use expand-to-foreign-dyn as an example: If a translation method is available [for some defn thereof], as found by compute-applicable-methods, but that method answered *runtime-translator-form*, the final result of the expander would be something like `(multiple-value-bind (,var ,param) (translate-type-to-foreign ,value ,type) (unwind-protect (progn ,@body) (free-type-translated-object ,var ,type ,param))) Otherwise, both implementations of expand-type-to-foreign-dyn would short-circuit the generic function call and return `(let ((,var ,(expand-type-to-foreign value type))) ,@body) Though only if by similar heuristic they found that a one-way expander was available. I've rearranged things here to combine the cases, eliminate the *runtime-translator-form* exportation, and make the code simpler. Currently, both cases are collapsed into the former expansion. However, this breaks some misc-types.expand tests, as it breaks this guarantee listed in that file: Ensure that macroexpansion-time translators are called where this is guaranteed (defcfun, defcvar, foreign-funcall and defcallback) Now, expand-to-foreign is undocumented (:), so I am not sure what its semantics are supposed to be anyway. (In particular, I don't see whether the expand-type-* specializations for foreign-typedef are following the actual-type chain.) If it is precisely like a compiler macro, this can easily be fixed by changing translate-type-to-foreign to expand-type-to-foreign in the current expansion, and things will work nicely. However, I must be able to call free-type-translated-object on the results of the forward-expanded form for this to work. Can I rely on this guarantee, so that I can in return reoffer the aforementioned guarantee? -- Stephen Compall http://scompall.nocandysw.com/blog

2 13

[cffi-devel] sbcl on mingw: Test CFFI-TESTS::DEFCFUN.UNDEFINED failed
by Yaroslav Kavenchuk 30 Mar '06

30 Mar '06

SBCL 0.9.9.37 on mingw, cffi-060225.tar.gz * (asdf:operate 'asdf:load-op :cffi) ... Test CFFI-TESTS::DEFCFUN.UNDEFINED failed Form: (PROGN (EVAL '(CFFI:DEFCFUN "undefined_foreign_function" :VOID)) (COMPILE 'CFFI-TESTS::UNDEFINED-FOREIGN-FUNCTION) T) Expected value: T Actual value: #<UNDEFINED-ALIEN-ERROR undefined_foreign_function {B45E8E9}>. Thanks. -- WBR, Yaroslav Kavenchuk.

3 5

[cffi-devel] A slight documentation disambiguation?
by Samium Gromoff 29 Mar '06

29 Mar '06

Apropos the built-in types section, would it make sense to replace a slightly ambiguous sentence mixing three things: "On most systems, the :float type represents a C float and a Lisp single-float. :double represents a C double and a Lisp double-float." with two separate sentences: "On all systems the :float type represents a C float, :double represents a C double." and "On most systems, the :float type a Lisp single-float, :double represents a Lisp double-float." ? respectfully, Samium Gromoff

2 1

[cffi-devel] New patches: 27-Mar-2006
by loliveira＠common-lisp.net 28 Mar '06

28 Mar '06

Mon Mar 27 19:49:44 EST 2006 Stephen Compall <scompall(a)nocandysw.com> * manual-don't use PRINT-OBJECT for CONDITIONs M ./doc/cffi-manual.texinfo -8 +5 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060327.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] cffi macro suggestion
by hbabcockos1＠mac.com 26 Mar '06

26 Mar '06

Hello, I've been working on an interface for the graphics package plplot (http://plplot.sourceforge.net/) Its API has lots of functions that expect arrays, matrixes and associated variables that specify the size of the array/matrix. To facilitate wrapping these functions I wrote a macro that I thought might (after some modification/cleaning) be useful for others. The macro can be found at: http:// paste.lisp.org/display/18274. It was written to expand a function declaration like: (pl-defcfun ("c_plmesh" plmesh) :void (x *plflt nx) (y *plflt ny) (z **plflt (nx ny)) (nx plint) (ny plint) (opt plint)) into: (progn statements removed) (DEFCFUN ("c_plmesh" C-PLMESH) :VOID (X *PLFLT) (Y *PLFLT) (Z **PLFLT) (NX PLINT) (NY PLINT) (OPT PLINT)) (EXPORT 'C-PLMESH (PACKAGE-NAME *PACKAGE*))) (DEFUN PLMESH (X Y Z OPT) (LET ((C-X (MAKE-PTR X :DOUBLE #'(LAMBDA (X) (COERCE X 'DOUBLE- FLOAT)))) (C-Y (MAKE-PTR Y :DOUBLE #'(LAMBDA (X) (COERCE X 'DOUBLE- FLOAT)))) (NX (ARRAY-DIMENSION Z 0)) (NY (ARRAY-DIMENSION Z 1)) (C-Z (MAKE-MATRIX Z))) (UNWIND-PROTECT (C-PLMESH C-X C-Y C-Z (FUNCALL #'(LAMBDA (X) (ROUND X)) NX) (FUNCALL #'(LAMBDA (X) (ROUND X)) NY) (FUNCALL #'(LAMBDA (X) (ROUND X)) OPT)) (PROGN (FOREIGN-FREE C-X) (FOREIGN-FREE C-Y) (FREE-MATRIX C-Z (LIST NX NY)))))) (EXPORT 'PLMESH (PACKAGE-NAME *PACKAGE*)))) Where make-ptr, make-matrix and free-matrix are functions that make 1D arrays, make 2D arrays & free 2D arrays respectively. best, -Hazen

2 2

[cffi-devel] cffi not working on x86-64 with cmucl (working with sbcl)
by Dawgmatix 24 Mar '06

24 Mar '06

Lisp: CMUCL version 19c OS: ubuntu dapper 64 bit CFFI: from darcs as of today I tried loading cl-opengl as well as load libGL.so manually. It does not work. On the same system with sbcl 0.9.10 both loading libraries and cl-opengl DO work. I am unable to dig further because the error only tells me that the library could not be loaded. Regards, Deep

2 1

[cffi-devel] Can't expand foreign-funcall
by Liam M. Healy 22 Mar '06

22 Mar '06

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=335185560… Liam

2 2

[cffi-devel] trapping C exit
by hbabcockos1＠mac.com 21 Mar '06

21 Mar '06

Hi, Is there a way to trap a call to exit made in a C library and prevent it from stopping the currently running Lisp process? I'm struggling with an annoying C library function that was written to call exit() if it didn't get the arguments that it expected (or sometimes to call exit() even if it did get the expected arguments). I.e, how would I wrap this CFFI function so that calling it won't stop my lisp process? (defcfun ("exit" exit) :void (code :int)) Thanks, -Hazen

2 1

Fwd: [cffi-devel] Array call crashes SBCL on one computer
by Liam M. Healy 19 Mar '06

19 Mar '06

Stephen> On Sun, 2006-03-19 at 12:53 -0500, Liam M. Healy wrote: >> - The desktop is ..., Darcs pull 2006-03-07 23:11, SBCL 0.9.8.42 >> - The laptop is ..., Darcs pull 2006-03-17 23:59, SBCL 0.9.9 Stephen> This may or may not be an issue. >> (with-foreign-objects ((retn :double)) >> (foreign-funcall "gsl_sf_bessel_Jn_array" >> :int 0 >> :int 2 >> :double 0.25d0 >> :pointer retn >> :int) >> (mem-aref retn :double 0)) Stephen> I know nothing about GSL besides what I just read about the function you Stephen> call above, but don't you need to allocate space for 3 doubles, not just Stephen> one, for the retn (result_array) argument? Yes, that's it. For some reason, one is OK with the lack of allocation, the other is not. Thanks. Liam

2 1

[cffi-devel] Array call crashes SBCL on one computer
by Liam M. Healy 19 Mar '06

19 Mar '06

I have two computers, both Linux/x386. - The desktop is Debian unstable, Darcs pull 2006-03-07 23:11, SBCL 0.9.8.42 - The laptop is Ubuntu 05.10, Darcs pull 2006-03-17 23:59, SBCL 0.9.9 On both I have GSL (libgsl0) installed, which includes two libraries /usr/lib/libgslcblas.so.0 /usr/lib/libgsl.so.0 which I have made links to the corresponding .so names. On each I do: (require :asdf) (require :cffi) (in-package :cffi) (cffi:load-foreign-library "/usr/lib/libgslcblas.so") (cffi:load-foreign-library "/usr/lib/libgsl.so") (with-foreign-objects ((retn :double)) (foreign-funcall "gsl_sf_bessel_Jn_array" :int 0 :int 2 :double 0.25d0 :pointer retn :int) (mem-aref retn :double 0)) On the desktop, everything works normally and I get 0.9844359292958527d0 On the laptop, I get an SBCL crash with the following message: Argh! corrupted error depth, halting fatal error encountered in SBCL pid 29184(tid 3085391552): %PRIMITIVE HALT called; the party is over. The system is too badly corrupted or confused to continue at the Lisp level. If the system had been compiled with the SB-LDB feature, we'd drop into the LDB low-level debugger now. But there's no LDB in this build, so we can't really do anything but just exit, sorry. Some other results on the laptop: - All functions I've tried that return a pointer to an array of doubles have this problem. - Sometimes the problem behavior varies. For example, If the third argument is 0.5d0, SBCL simply locks up instead of crashing. Sometimes I get an infinite output of error messages that repeat the line "mprotect: Cannot allocate memory" over and over. Any debugging advice? Thanks. Liam

2 1

[cffi-devel] New patches: 16-Mar-2006
by loliveira＠common-lisp.net 17 Mar '06

17 Mar '06

Thu Mar 16 06:55:05 EST 2006 Stephen Compall <scompall(a)nocandysw.com> * small manual fixes - Add convert-to-foreign, convert-from-foreign, and free-converted-object to the master menu. - (load-foreign-library): Add note about specifying directories in paths. - (defcfun): Typo in syntax. M ./TODO -2 M ./doc/cffi-manual.texinfo -6 +14 Thu Mar 16 06:45:54 EST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Lispworks: use regression-test instead of rt. M ./tests/callbacks.lisp -2 +2 Thu Mar 16 06:40:28 EST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * SCL update + new cffi-sys primitive - New cffi-sys primitive: canonicalize-symbol-name-case. Use this instead of read-from-string. Also new tests for this. - cffi-scl.lisp: correct the evaluation order of %MEM-REF and %MEM-SET. Have 'foreign-symbol-pointer return 'nil if the symbol is not found. - uffi-compat.lisp: better support for SCL. - defcfun.lisp (defcfun.undefined): package at time of eval may differ from the compile time package. Patch courtesy of Douglas Crosher. M ./src/cffi-allegro.lisp +9 M ./src/cffi-clisp.lisp +7 M ./src/cffi-cmucl.lisp +7 M ./src/cffi-corman.lisp +7 M ./src/cffi-ecl.lisp +7 M ./src/cffi-gcl.lisp +7 M ./src/cffi-lispworks.lisp +7 M ./src/cffi-openmcl.lisp +7 M ./src/cffi-sbcl.lisp +7 M ./src/cffi-scl.lisp -14 +24 M ./src/foreign-vars.lisp -5 +3 M ./src/functions.lisp -1 +1 M ./tests/foreign-globals.lisp +84 M ./tests/libtest.c +19 M ./uffi-compat/uffi-compat.lisp -12 +16 Thu Mar 16 06:28:18 EST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * when (and ecl (not dffi)) cffi:load-foreign-library doesn't work - mention this in the manual. - make l-f-l signal an error on non-dffi ecl platforms. M ./doc/cffi-manual.texinfo +11 M ./src/cffi-ecl.lisp -1 +3 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060316.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] Re: unnamed callback (closures?)
by Jan Rychter 16 Mar '06

16 Mar '06

[resending directly as it seems messages posted through Gmane don't make it to the list :-/ ] >>>>> "Luís" == Luís Oliveira <luismbo(a)gmail.com>: Luís> "Hoehle, Joerg-Cyril" <Joerg-Cyril.Hoehle(a)t-systems.com> writes: >> In CLISP, every closure can be turned into a callback, and this is >> valuable since it allows to retrieve context information out of the >> closure. Is cffi's limitation caused by some implementations? Luís> To my knowledge, yes. AFAICT, only SBCL/x86 and CLISP support Luís> that. Luís> Regarding the behaviour of CFFI:DEFCALLBACK as a non-toplevel Luís> form, not only will it set it globally, the callback itself won't Luís> be generated at runtime on most Lisp, IIRC. I've just ran into the same problem. I really really need closures as callbacks. I've tried the naive approach: (defmacro object-event-callback-add (obj type function) `(foreign-funcall "evas_object_event_callback_add" :pointer ,obj callback-type ,(foreign-enum-value 'callback-type type) :pointer (get-callback (defcallback ,(gensym "CB") :void ((data :pointer) (cb-e evas) (cb-obj object) (cb-event :pointer)) (funcall ,function cb-e cb-obj cb-event))) :pointer (null-pointer))) ... but that's a half-baked solution with too many limitations and only works in a simple example that you run once. What are the problems with unnamed callbacks? My guess was that they will never get garbage-collected, but how about storing all of these in a table somewhere and explicitly freeing them after they are no longer needed? In my case I do have a way of finding out when a callback is no longer needed, and I suspect this is the case for many other applications. I mostly develop on SBCL/x86 and ECL, so even if a solution worked on these platforms only, I'd be really happy. --J.

5 12

[cffi-devel] [patch] small manual updates
by Stephen Compall 16 Mar '06

16 Mar '06

Been trying to work on code for the past week or so, so not many manual changes since the last one. Anyway, here are a few fixes: Wed Mar 15 13:18:49 CST 2006 Stephen Compall <scompall(a)nocandysw.com> * small manual fixes - Add convert-to-foreign, convert-from-foreign, and free-converted-object to the master menu. - (load-foreign-library): Add note about specifying directories in paths. - (defcfun): Typo in syntax. -- Stephen Compall http://scompall.nocandysw.com/blog

2 2

[cffi-devel] creating two-dimensional arrays
by hbabcockos1＠mac.com 16 Mar '06

16 Mar '06

Hello, What is the right way to create a 2D array to pass to a c-function that expects **arr? I tried: (defun make-matrix (lisp-mat) "Creates a two-dimensional c array, initializes with lisp matrix" (let* ((x-dim (array-dimension lisp-mat 0)) (y-dim (array-dimension lisp-mat 1)) (c-mat (foreign-alloc :pointer :count y-dim))) (dotimes (y y-dim) (let ((cur (foreign-alloc :double :count x-dim))) (setf (mem-aref c-mat :pointer y) cur) (dotimes (x x-dim) (setf (mem-aref cur :double y) (coerce (aref lisp-mat x y) 'double-float))))) c-mat)) To pass the argument z to the c-function: c_plmesh(PLFLT *x, PLFLT *y, PLFLT **z, PLINT nx, PLINT ny, PLINT opt); (PLFLT is of type double & PLINT is of type int) But some of the values appear to get mangled in transit. Thanks, -Hazen (CFFI 0.9.0, SBCL 0.9.9, OS-X 10.4)

2 2

[cffi-devel] char** ??
by Goenninger, Frank 15 Mar '06

15 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all you CFFI hackers: I am currently trying to get GLUT to work via CFFI. There I have the following C function declaration: extern void glutInit(int *argcp, char **argv); Hmm - now I am asking myself: 1. Do I have to define a new type as Integer Pointer ? Same also for char ** ? 2. How do I avoid defining new types while still being able to define this function via defcfun ? Or, in other words, how would you define this function with defcfun ?? Thanks for any pointers ;-) Cheers, Frank -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.5 (Build 5050) iQIVAwUBRBhcyGAKVUddnkqnAQrPUQ//TegvAbvahD9igy7yPtvdWnk92tv96wTt 9QafBaFtLHnxOevR9s5J+KhXSz512Vhtt73MaNAll69wbZJKCl9ZD9taTXfnRhbk AA4Am3YZAPl8/QyMVKLwuDjkd9as+MIVWimcJrah/9Bi+h0/ySWlxAoYcP8XCz48 zMjp5LDVqupJ17nnLpwawn9FbSN2sGXjP3K8wlzdrlrVQnWHvS0+6ln1ioDrjH3Z 9V9HvCYO1diJc56T0lPmDVzK9tNyyljpvy8Ga3ePvRRvTToaYeXhXI1fkioYgmya PZN44hNivPYMmY4cpVbOzPmQg63JqTnHqxSIuaqa/rf60s0q/0zCiBji+GTSfIrw k38ucmEJqzd+p9Us6qISxwvTMc6+E4HUoH7KBAtMkleUk7hOSnjMO3WvB+jefRki YFk56e/bwTW+MPre/96xefGSXeDvJ3+h/mlmKCF+Ug2s5tOikk45YiFl9iwSaB00 KKjUkVym9rVzN1iDVk9QgiiB2evpYejrTi62A4qUz20d12+BpegEPgEmo3swOpS4 ypKn6sWYLduQ46kkap87+ZJz9hqa37JmOTzk4gMYryR9FJ5OXeBo0BKMHAkn17gf fA5EuskNfg7t5A+BSB18bA1VaSXvSvyryIcm7elHuQPkWSy0nwd81dFrhqYzxdxX dr2D0uRLokk= =Z2cP -----END PGP SIGNATURE-----

3 2

[cffi-devel] New patches: 13-Mar-2006
by loliveira＠common-lisp.net 14 Mar '06

14 Mar '06

Tue Feb 28 23:33:49 EST 2006 Stephen Compall <scompall(a)nocandysw.com> * manual: convert-* interface, optimizing translators overview optimized - (Wrapper generators): Add comment about the 30-90% figure. - Reword `Pointers' to be shorter/clearer. - Promote `Optimizing Type Translators' to a full section, a few other things here, most conspicuously expanding on the note about expand-* method definition time. - (Tutorial-Conclusion): Not a first draft anymore. - Document convert-to-foreign, convert-from-foreign, and free-converted-object. M ./doc/cffi-manual.texinfo -40 +226 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060313.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] manual: convert-* interface, optimizing translators overview
by Stephen Compall 13 Mar '06

13 Mar '06

Darcs patch at http://csserver.evansville.edu/~sc87/cffi/convert-and-expand-doc-6s11.darcs… Tue Feb 28 22:33:49 CST 2006 Stephen Compall <scompall(a)nocandysw.com> * manual: convert-* interface, optimizing translators overview optimized - (Wrapper generators): Add comment about the 30-90% figure. - Reword `Pointers' to be shorter/clearer. - Promote `Optimizing Type Translators' to a full section, a few other things here, most conspicuously expanding on the note about expand-* method definition time. - (Tutorial-Conclusion): Not a first draft anymore. - Document convert-to-foreign, convert-from-foreign, and free-converted-object. -- Stephen Compall http://scompall.nocandysw.com/blog

2 1

[cffi-devel] question about defcfun
by Hazen Babcock 01 Mar '06

01 Mar '06

Hello, I'm having some difficulty passing arguments to defcfun. This is likely due to my incomplete knowledge of lisp, so hopefully someone can point me in the right direction. Given the following code: defpackage :cffi-test (:use :common-lisp :cffi)) (in-package :cffi-test) (defun strip-args (args) (let ((new-args nil)) (dolist (elm (car args)) (setf new-args (append new-args (list (subseq elm 0 2))))) new-args)) (defun make-defcfun-call (c-name lisp-name returns &rest args) `(defcfun (,c-name ,lisp-name) ,returns ,@(strip-args args))) (defmacro pl-defcfun (name returns &rest args) (make-defcfun-call (elt name 0) (elt name 1) returns args)) (defmacro pl-defcfun-2 (name returns &rest args) (make-defcfun-call (elt name 0) (make-symbol (format nil "bar- ~A" (elt name 1))) returns args)) This creates a function called l-foo: (pl-defcfun ("c-foo" l-foo) :void (x :char) (y :char)) This should create a function call bar-l-foo (or maybe #|bar-l- foo|?), but doesn't appear to (as judged by my not getting a function prototype at the slime REPL). (pl-defcfun-2 ("c-foo" l-foo) :void (x :char) (y :char)) Maybe defcfun is not getting the right kind of symbol? I am running SBCL 0.9.9 with a few week old version of slime from cvs on OS-X 10.4. Thanks for your help, -Hazen

2 1

[cffi-devel] New patches: 28-Feb-2006
by loliveira＠common-lisp.net 01 Mar '06

01 Mar '06

Tue Feb 28 14:36:23 EST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Remove known issues sub-section from the manual. - Listing the expected failures in the manual is too much trouble. Removed those. - Also, renamed "The Scieneer Common Lisp" to "Scieneer CL" for consistency. M ./doc/cffi-manual.texinfo -70 +26 Tue Feb 28 14:16:42 EST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * TODO item about a pointer type, suggested by Jörg Höhle M ./TODO +3 Tue Feb 28 11:26:38 EST 2006 Stephen Compall <scompall(a)nocandysw.com> * manual: strings, foreign allocation, add `Wrapper generators' - Explain the difference between mem-aref and mem-ref by analogy with C operators. - Use ::= instead of = in with-foreign-object's syntax. - (Strings): Explain that it is portable code. - (Other Types): Don't use metasyntactic variables in Lisp examples. - Add `Wrapper generators' section on Verrazano et al. - (Foreign Type Translators): Use Please note: instead of Note: to suppress makeinfo warning. M ./doc/cffi-manual.texinfo -12 +77 Mon Feb 27 14:48:54 EST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * More testing - Make defcfun.undefined an expected failure for SBCL on non linkage-table platforms. - New file: tests/misc.lisp. - Added a couple of tests for cffi-features. M ./cffi-tests.asd -1 +2 M ./tests/defcfun.lisp -3 +5 A ./tests/misc.lisp Mon Feb 27 14:48:13 EST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * TODO item about our use of EVAL M ./TODO -1 +3 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060228.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0