cffi-devel

cffi-devel@common-lisp.net

1113 discussions

[cffi-devel] Lisp/CFFI interface to Midishare available
by Rick Taube 16 Dec '05

16 Dec '05

A CFFI interface to Midishare for Common Lisp is available for download from Common Music's Sourceforge project area: http://sourceforge.net/project/showfiles.php? group_id=9766&package_id=172112 The interface should work in (at least) the following Lisp implementations: clisp 2.35 openmcl 1.0 cmucl 19c sbcl 0.9.7 The interface code does not depend at all on Common Music. Midishare: http://midishare.sf.net/ CFFI: http://common-lisp.net/project/cffi/ Common Music: http://commonmusic.sf.net/ Rick Taube Associate Professor, Composition/Theory School of Music University of Illinois, Urbana IL 61821 USA Net: taube@uiuc Fax: 217 244 8319 Vox: 217 244 2684

2 4

[cffi-devel] running examples - errors?
by Surendra Singhi 15 Dec '05

15 Dec '05

Hello, I am having trouble running the cffi examples on clisp/allegrocl on windows xp. (cffi-luis-050925-2059) First of all do I need some dll or library to run the examples? The tar ball doesn't contain anything. When I load the file through slime I get the error FFI::FOREIGN-LIBRARY-FUNCTION: no dynamic object named "sqrtf" in library :DEFAULT but loading on the command line works fine. But if from the command line I execute, [3]> (cffi-examples:sqrtf 5) *** - FFI::FOREIGN-LIBRARY-FUNCTION: no dynamic object named "sqrtf" in library :DEFAULT The following restarts are available: USE-VALUE :R1 You may input a value to be used instead. ABORT :R2 ABORT Break 1 [4]> :R2 [6]> (cffi-examples:gettimeofday) *** - FFI::FOREIGN-LIBRARY-FUNCTION: no dynamic object named "gettimeofday" in library :DEFAULT The following restarts are available: USE-VALUE :R1 You may input a value to be used instead. ABORT :R2 ABORT Break 1 [7]> Only gethostname function seems to work. Thanks. -- Surendra Singhi http://www.public.asu.edu/~sksinghi/index.html "All animals are equal, but some animals are more equal than others." - Orwell, Animal Farm, 1945

3 6

[cffi-devel] Validate auto-generated wrappers
by Surendra Singhi 14 Dec '05

14 Dec '05

Hi, I wrote a quick swig hack to parse c files and generate cffi headers. I will appreciate if you can verify them, and suggest me how can I improve the auto-generated headers, or if you can give me some test cases. Disclaimer: I am not very familiar with cffi, so if I am making any obvious mistakes please point out. The C input file: ----------------------------------------------------------- char *s; }; struct cfunr * cfun (int i,char *s,struct cfunr * r,int a[10]) { int j; struct cfunr * r2; printf("i = %d\n", i); printf("s = %s\n", s); printf("r->x = %d\n", r->x); printf("r->s = %s\n", r->s); for (j = 0; j < 10; j++) printf("a[%d] = %d.\n", j, a[j]); r2 = (struct cfunr *) malloc (sizeof (struct cfunr)); r2->x = i+5; r2->s = "A C string"; return r2; } void* lispsort_function(int); void lispsort_double (int n, double * array) { double * sorted_array; int i; lispsort_begin(n); /* store #'sort2 in lispsort_function */ sorted_array = ((double * (*) (double *)) lispsort_function) (array); for (i = 0; i < n; i++) array[i] = sorted_array[i]; free(sorted_array); } void test(float x , double y); } --------------------------------------------------------------------- _The auto-generated lisp file (indentation and spacing fixed)_ --------------------------------------------------------------------------- ;; This is an automatically generated file. ;;Make changes as you feel are necessary (but remember if you try to regenerate this file, your changes will be lost). (defpackage :test (:use :common-lisp :cffi) (:export :max :acbdsqr_ :make-bar :bar-x :bar-y :bar-a :bar-b :bar-z :bar-n :my_struct :make-foo :foo-a :foo-b :pointer_func :make-div_t :div_t-quot :div_t-rem :func123 :func1234 :make-cfunr :cfunr-x :cfunr-s :cfun :lispsort_function :lispsort_double :test)) (in-package :test) (defconstant max 1000) (defcfun ("acbdsqr_" acbdsqr_) :void (xyz :pointer)) (defcstruct bar (x :short) (y :short) (a :char) (b :char) (z :pointer) (n :pointer)) (def-c-var ("my_struct" my_struct) :pointer) (defcstruct foo (a :int) (b :pointer)) (defcfun ("pointer_func" pointer_func) :int (ClosureFun :pointer) (y :int)) (defcstruct div_t (quot :int) (rem :int)) (defcfun ("func123" func123) :int (x :pointer) (z :pointer) (y :pointer)) (defcfun ("func1234" func1234) :void (x :pointer)) (defcstruct cfunr (x :int) (s :string)) (defcfun ("cfun" cfun) :pointer (i :int) (s :string) (r :pointer) (a :pointer)) (defcfun ("lispsort_function" lispsort_function) :pointer (arg0 :int)) (defcfun ("lispsort_double" lispsort_double) :void (n :int) (array :pointer)) (defcfun ("test" test) :void (x :float) (y :double)) ---------------------------------------------------------------- -- Surendra Singhi http://www.public.asu.edu/~sksinghi/index.html The best-laid plans of mice and men go oft astray.

2 1

[cffi-devel] small bag in cffi-uffi-compat
by Леонид Новиков 14 Dec '05

14 Dec '05

I have found small mistake in cffi-uffi-compat: CL-USER> (cffi-uffi-compat:def-struct g-value (g-type (:array :int 16))) G-VALUE CL-USER> (cffi-uffi-compat::convert-uffi-type 'g-value) G-VALUE CL-USER> (cffi-uffi-compat::convert-uffi-type '(:array 'g-value)) (CFFI-UFFI-COMPAT::UFFI-ARRAY NIL NIL) Last call was to return: (CFFI-UFFI-COMPAT::UFFI-ARRAY G-VALUE NIL) For correct work I have corrected convert-uffi-type as follows: (defun convert-uffi-type (uffi-type) "Convert a UFFI primitive type to a CFFI type." ;; Many CFFI types are the same as UFFI. This list handles the ;; exceptions only. (case uffi-type (:cstring :pointer) (:pointer-void :pointer) (:pointer-self :pointer) (:char '(uffi-char :char)) (:unsigned-char '(uffi-char :unsigned-char)) (:byte :char) (:unsigned-byte :unsigned-char) (t (if (listp uffi-type) (case (car uffi-type) (* :pointer) (:array `(uffi-array ,(convert-uffi-type (second uffi-type)) ,(third uffi-type))) (:union (second uffi-type)) (:struct (convert-uffi-type (second uffi-type))) (:struct-pointer :pointer) ;My correction (t (eval uffi-type)) ) uffi-type)))) I bad know lisp so probably this not best variant of the decision of this mistake.

2 4

[cffi-devel] gccxml install?
by C Y 13 Dec '05

13 Dec '05

I took a run last night at getting the fltk demo working, and the generate step fails with a complaint about gccxml not working. However, gccxml is in my path. Do I need to put the fltk source tree in the test directory or some other trivial problem? I'm quite sure this is something dumb but I'm not sure how to check it - the error message is not all that helpful :-/. Cheers, CY __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: [cffi-devel] mid-level implementation-specific patches (was: uffi and CUSTOM:* FOREIGN-ENCODING* from clisp)
by Hoehle, Joerg-Cyril 12 Dec '05

12 Dec '05

Hi, Luís Oliveira wrote: >Also we need to handle encodings. That's really important. I almost feel sorry for wasting your time on small optimization issues when there are much more important things to do. >Right, once the block memory interface is implemented for all Lisps, >we can optimize strings.lisp Block operations are no silver bullet either. E.g. with-foreign-string maps nicely to CLISP's ffi:with-foreign-string. Using block operations instead would still do more work (and it's unclear whether block operations would work fast in CLISP with strings or rather arbitrary encodings, or whether the block code would resort to a LOOP). James Bielman wrote: >how about adding >"cffi/src/optimizers-clisp.lisp" (and associated files for other >implementations) that use compiler macros to perform the optimization? It's maybe the best one can do given your preference for implementation-specific files. Yet I felt somewhat strange about writing compiler-macros for macros (e.g. with-xyz), not functions. The typical counter argument is risk of drift between the two files containing the original function or code and the other with the macro optimizer. So far, the cffi-impl.lisp files which contain both a low-level function, followed by the optimizer version are very nice to review. One immediately sees the correspondance between the two forms. There's no risk that somebody will edit one and forget to edit the other. That's very different with code spread across files. Especially, handling of border cases may then vary across implementations. E.g. I remember having to modify my version of uffi:with-cstrings to accept an empty list of bindings: all optimizers would need to be modified similarly. Regards, Jörg Höhle.

1 0

[cffi-devel] Trivial GTK/CFFI test
by tarka＠internode.on.net 12 Dec '05

12 Dec '05

Hi, I was trying out CFFI at the weekend and was pleasantly surprised at how simple it was to create some simple bindings to GTK: http://people.vislab.usyd.edu.au/~ssmith/lisp/cffi-gtk-test.lisp What's interesting to me is that rather than relying on third-party bindings it is reasonable to just add your own as-needed, as creating a binding manually is no more work than actually using it. Thanks for the good work. Cheers, Steve

3 8

[cffi-devel] [feature request] array type
by Jack Unrue 11 Dec '05

11 Dec '05

Hello! Has there been any more thought put into the possibility of defining an array type? Having read the list archives, I'm aware that this has been proposed: http://common-lisp.net/pipermail/cffi-devel/2005-September/000057.html I can certainly help test on various Lisp implementations, and with some guidance into how types are defined in CFFI, I'm willing to contribute some patches. Thanks. -- Jack Unrue

2 4

[cffi-devel] patch for uffi-compat
by Yaroslav Kavenchuk 11 Dec '05

11 Dec '05

Sorry, but I do not see in mail-list my first message. This is double uffi 1.5.5 is out This patch add new function from it File uff-compat.diff ========================================== --- uffi-compat.lisp Fri Nov 4 12:12:12 2005 +++ uffi-compat.lisp Fri Nov 4 23:47:42 2005 @@ -91,6 +91,7 @@ ;; os #:run-shell-command + #:getenv )) (in-package #:cffi-uffi-compat) @@ -503,6 +504,35 @@ ;; Taken from UFFI's src/os.lisp ;; modified from function ASDF -- Copyright Dan Barlow and Contributors +(defun getenv (var) + "Return the value of the environment variable." + #+allegro (sys::getenv (string var)) + #+clisp (sys::getenv (string var)) + #+cmu (cdr (assoc (string var) ext:*environment-list* :test #'equalp + :key #'string)) + #+gcl (si:getenv (string var)) + #+lispworks (lw:environment-variable (string var)) + #+lucid (lcl:environment-variable (string var)) + #+mcl (ccl::getenv var) + #+sbcl (sb-ext:posix-getenv var) + #-(or allegro clisp cmu gcl lispworks lucid mcl sbcl) + (error 'not-implemented :proc (list 'getenv var))) + +(defun (setf getenv) (val var) + "Set an environment variable." + #+allegro (setf (sys::getenv (string var)) (string val)) + #+clisp (setf (sys::getenv (string var)) (string val)) + #+cmu (let ((cell (assoc (string var) ext:*environment-list* :test #'equalp + :key #'string))) + (if cell + (setf (cdr cell) (string val)) + (push (cons (intern (string var) "KEYWORD") (string val)) ext:*environment-list*))) + #+gcl (si:setenv (string var) (string val)) + #+lispworks (setf (lw:environment-variable (string var)) (string val)) + #+lucid (setf (lcl:environment-variable (string var)) (string val)) + #-(or allegro clisp cmu gcl lispworks lucid) + (error 'not-implemented :proc (list '(setf getenv) var))) + (defun run-shell-command (control-string &rest args &key output) "Interpolate ARGS into CONTROL-STRING as if by FORMAT, and synchronously execute the result using a Bourne-compatible shell, with

2 1

[cffi-devel] Lisp/CFFI interface to Portmidi available
by Rick Taube 10 Dec '05

10 Dec '05

A CFFI interface to Portmidi for Common Lisp is available for download from Common Music's Sourceforge project area. http://sourceforge.net/project/showfiles.php? group_id=9766&package_id=172088 The interface should work in (at least) the following Lisp implementations: clisp 2.35 openmcl 1.0 cmucl 19c sbcl 0.9.7 The interface code does not depend at all on Common Music. Portmidi: http://www-2.cs.cmu.edu/~music/portmusic/ CFFI: http://common-lisp.net/project/cffi/ Common Music: http://commonmusic.sf.net/ Rick Taube Associate Professor, Composition/Theory School of Music University of Illinois, Urbana IL 61821 USA Net: taube@uiuc Fax: 217 244 8319 Vox: 217 244 2684

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel