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

[cffi-devel] Mutable Pointers
by Stuart Sierra 14 Jul '06

14 Jul '06

Hello, I'm working on a CFFI interface to the Perl API (I thought it would be fun - ha!) and I need to be able to do C-style pointer arithmetic. That is, I have a foreign pointer declared with DEFCVAR and I need to alter the address stored there. I couldn't see a way to do this with CFFI, so I created a new foreign type called :ADDRESS that would treat the foreign pointer as an integer value that I could modify. Here's my code: (defvar *pointer-size* (foreign-type-size :pointer) "The size of a pointer on the current platform, in bytes.") (ecase *pointer-size* (1 (defctype :address :uint8)) ; unlikely (2 (defctype :address :uint16)) ; possible (4 (defctype :address :uint32)) ; most common (8 (defctype :address :uint64))) ; possible (defmacro address-incf (address &optional (n 1)) "Increment ADDRESS by N pointers, like ++i on a C pointer." `(incf ,address (* ,n *pointer-size*))) (defmacro address-decf (address &optional (n 1)) "Decrement ADDRESS by N pointers, like --i on a C pointer." `(decf ,address (* ,n *pointer-size*))) (defmacro address-ref (address type) "Dereference ADDRESS to get the TYPE it points to, like MEM-REF." `(mem-ref (make-pointer ,address) ,type)) This does work for my purposes, but is there a better way using CFFI internals? Thanks, -Stuart

4 9

Re: [cffi-devel] trying to understand foreign types and translations
by rif 06 Jul '06

06 Jul '06

> The two arguments to TRANSLATE-TO-FOREIGN are the Lisp object to be > converted, and the name of the foreign type to convert to. First, > declare a foreign typedef for :POINTER (since you will ultimately be > returning a pointer from the type translator) that you use to hang > your type translator on: > > (defctype fnv-double :pointer) > > Then you can specialize TRANSLATE-TO-FOREIGN on both the Lisp value > and the foreign type (using an EQL specializer): > > (defmethod translate-to-foreign ((value fnv-double) (name (eql 'fnv-double))) > (fnv-foreign-pointer value)) > > It might be confusing to call both the Lisp and foreign types > FNV-DOUBLE, but it is legal because foreign type names are a separate > namespace from Lisp types (viva Lisp-N!). It is important to remember > the distinction between the two though. > > > and then declaring something like > > > > (defcfun ("foo" :%foo) :double > > (x fnv-double)) > > should just work! > > (This is untested and I haven't really been doing any CFFI hacking > lately, so I apologize if I missed something obvious here.) > > James I don't quite understand. fnv-double is NOT a pointer. It's a CL struct that holds two arguments, one of which is the foreign pointer. I see I was misusing translate-to-foreign, so maybe I don't need a defctype at all, just an appropriate translate-to-foreign? rif

2 1

[cffi-devel] trying to understand foreign types and translations
by rif 06 Jul '06

06 Jul '06

I've been poking at this for over an hour, but I'm just not sure how to get this to work. I have a foreign object, points to a vector of (C) double-floats: (defstruct (fnv-double (:constructor make-fnv-double-internal)) (foreign-pointer nil :read-only t) (size 0 :type fixnum :read-only t)) I can create and manipulate it. I need to know how to define (with defcfun) an interface to a C function which expects a vector of double-floats. My attempts have been along the lines of: (defmethod translate-to-foreign (val (f fnv-double)) (fnv-foreign-pointer f)) and then declaring something like (defcfun ("foo" :%foo) :double (x fnv-double)) but neither this nor any of the variants I've tried seems to work at all. I think I need to either defctype or define-foreign-type first, but I haven't gotten that to work either. Can anyone suggest how to do this? Cheers, rif

2 1

[cffi-devel] Chase Online. Banking Account registration information
by Chase＠common-lisp.net 03 Jul '06

03 Jul '06

1 0

[cffi-devel] callback-lambda
by Jan Rychter 29 Jun '06

29 Jun '06

Having been away from CFFI for several months, I thought I'd ask: what happened to callback-lambda? James Bielman implemented an interim solution, but it never made its way into mainline CFFI and I think has bitrotted by now. Any particular reason why? As for me, a working callback-lambda under SBCL (and later ECL) would be a MAJOR win. Even more so if I could avoid memory leaks by being able to delete callbacks when they're no longer needed. --J.

3 4

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

27 Jun '06

Mon Jun 26 21:18:58 EDT 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Add long-long support to CLISP Patch courtesy of Frédéric Jolliton. M ./src/cffi-clisp.lisp -6 +6 Mon Jun 26 21:05:20 EDT 2006 Luis Oliveira <loliveira(a)common-lisp.net> * ECL fixes - cffi-ecl fixes: - push cffi-features:unix on darwin too. - use si:load-foreign-module instead of ffi:load-foreign-library on DFFI platforms. - use convert-external-name in foreign-symbol-pointer. - wrap defcvar's define-foreign-symbol around eval-when. - simplify default-library-suffix - cffi-tests: - load libtest.o on ECL platforms without DFFI. - conditionalize the tests with 127 arguments based on the value of lambda-parameters-limit. M ./TODO -1 +4 M ./src/cffi-ecl.lisp -7 +14 M ./src/foreign-vars.lisp -2 +5 M ./src/libraries.lisp -4 +2 M ./tests/bindings.lisp +6 M ./tests/callbacks.lisp -2 +4 M ./tests/defcfun.lisp -51 +55 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060626.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] [PATCH] Adding support for 64 bits types on CLISP > 2.38
by Frédéric Jolliton 27 Jun '06

27 Jun '06

Hi, Here is a trivial patch to enable 64 bits types on a recent CLISP version (newer than 2.38). I tested the latest CVS version, on Linux 2.6 x86-32. All the tests pass. However, I don't know how to test for the CLISP version to enable conditionally this support, because while at least CLISP 2.38 support ffi:uint64 and ffi:sint64 for function call parameters, it doesn't for return value of this type (it's accepted, but we get a random value.) --- cffi_0.9.1.orig/src/cffi-clisp.lisp 2006-04-11 22:02:54.000000000 +0200 +++ cffi_0.9.1/src/cffi-clisp.lisp 2006-06-26 02:46:01.000000000 +0200 @@ -63,7 +63,6 @@ (eval-when (:compile-toplevel :load-toplevel :execute) (mapc (lambda (feature) (pushnew feature *features*)) '(;; Backend mis-features. - cffi-features:no-long-long ;; OS/CPU features. #+macos cffi-features:darwin #+unix cffi-features:unix @@ -96,6 +95,8 @@ (:unsigned-int 'ffi:uint) (:long 'ffi:long) (:unsigned-long 'ffi:ulong) + (:long-long 'ffi:sint64) + (:unsigned-long-long 'ffi:uint64) (:float 'ffi:single-float) (:double 'ffi:double-float) ;; Clisp's FFI:C-POINTER converts NULL to NIL. For now -- Frédéric Jolliton

2 1

[cffi-devel] CFFI and ECL
by Juan Jose Garcia Ripoll 27 Jun '06

27 Jun '06

On Mon, 2006-06-26 at 14:06 +0100, Luís Oliveira wrote: > Heh, ECL/x86 too then. Cool. BTW, I still can't compile cffi-tests > due to the MAKE-LOAD-FORM bug though. (Well, I'm /assuming/ it's that > bug.) > > ;;; Loading "/Users/luis/src/cffi/tests/bindings.fas" > No dispatch function defined for character #\<. > Broken at LAMBDA. You probably used an old ECL. Our implementation can compile files with almost any kind of lisp object thanks to some patches contributed by Brian Spilsbury. I just "darc pull"'ed the latest sources from http://common-lisp.net/project/cffi/darcs/cffi and built it without problems. Indeed there are people using CFFI on ECL since a long time ago. See below how I build a single DLL for CFFI using a trick which is proper to our implementation. Regards, Juanjo --------- jlr@mpq3p59:~/src/lisp/cffi$ ecl ECL (Embeddable Common-Lisp) 0.9h Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya Copyright (C) 1993 Giuseppe Attardi Copyright (C) 2000 Juan J. Garcia-Ripoll ECL is free software, and you are welcome to redistribute it under certain conditions; see file 'Copyright' for details. Type :h for Help. Broken at EVAL. > (require 'asdf) ;;; Loading #P"/home/jlr/lib/ecl/asdf.fas" ("ASDF") > (asdf:make-build "cffi") ; loading system definition from cffi.asd into #<ASDF37 package> ;;; Loading "/home/jlr/src/lisp/cffi/cffi.asd" [...] NIL > (load "cffi.fas") ;;; Loading "/home/jlr/src/lisp/cffi/cffi.fas" ;;; Warning: Redefining class LOAD-FOREIGN-LIBRARY-ERROR [...] "/home/jlr/src/lisp/cffi/cffi.fas"

3 3

[cffi-devel] Message from eBay Member Regarding Item
by eBay＠common-lisp.net 19 Jun '06

19 Jun '06

1 0

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

14 Jun '06

Tue Jun 13 16:55:50 EDT 2006 Stephen Compall <scompall(a)nocandysw.com> * review Foreign Types; add Glossary M ./doc/cffi-manual.texinfo -34 +97 Wed May 17 16:12:39 EDT 2006 Nathan Bird <nathan(a)acceleration.net> * uffi-compat: in load-foreign-library, don't probe for file if no directory. If it is just a filename without a directory, continue passing it down to the underlying functions, as they probably know how to find a library in default location.s The test now matches the uffi behaviour too. M ./uffi-compat/uffi-compat.lisp -1 +3 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060613.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0