cffi-devel February 2006

cffi-devel@common-lisp.net

22 participants
65 discussions

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

17 Feb '06

Thu Feb 16 02:34:48 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Fix and add tests for %MEM-REF and %MEM-SET evaluation order. - Some minor reformatting of LOOP forms to pacify cl-indent. - Add new regression tests to check the evaluation order of %MEM-REF and %MEM-SET. - Add the necessary ONCE-ONLY forms to the compiler macros. - Have the CFFI-TESTS package use CFFI-SYS for testing primitives. M ./src/cffi-allegro.lisp -3 +4 M ./src/cffi-cmucl.lisp -10 +14 M ./src/cffi-lispworks.lisp -14 +16 M ./src/cffi-openmcl.lisp -10 +14 M ./src/cffi-sbcl.lisp -23 +27 M ./tests/memory.lisp +34 M ./tests/package.lisp -1 +1 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060216.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

Re: [cffi-devel] New patches: 3-Feb-2006: x86-64
by Hoehle, Joerg-Cyril 16 Feb '06

16 Feb '06

James Bielman writes: >Hmm, I've tried to install an x86 CLISP in a 32-bit chroot to prepare >to implement and test this, but I'm a little concerned about the fact >that MACHINE-TYPE still returns X86-64 on a 32-bit x86 build. Is >there a better way to tell whether we are running an x86 or x86-64 >CLISP? I'm sorry, I don't understand what you observed, what you want or what you need. Feel free to elaborate. Regards, Jorg Hohle.

2 1

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

16 Feb '06

Wed Feb 15 23:15:44 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Fix typo. extend -> extent M ./doc/cffi-manual.texinfo -1 +1 Wed Feb 15 23:07:35 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Minor change to tests/defcfun.lisp - Remove unnecessary (setf (mem-ref s :char) 0) forms. M ./tests/defcfun.lisp -7 Wed Feb 15 22:55:47 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * CFFI Manual update - Update known issues (callback.bff.[12] failures). - defbitfield, foreign-bitfield-symbols and foreign-bitfield-value. - Fix typo in tutorial. defenum -> defcenum. - New section "Other Types" documenting :string, :boolean and :wrapper. - Add note about the translate-* methods not being meant to be called directly and suggesting convert-* instead. - Document the macroexpansion-time translators in a new "Optimizing Type Translators" sub-section. - Document defcenum's base-type option. - Document defcfun's varargs support. M ./doc/cffi-manual.texinfo -15 +371 Wed Feb 15 22:53:35 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * New functions convert-to/from-foreign and free-converted-object - These functions basically export the functionality of translate-type-to-foreign, translate-type-from-foreign and free-translated-object. - TODO: document these. M ./TODO -3 +2 M ./src/package.lisp +3 M ./src/types.lisp +23 Wed Feb 15 22:52:40 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * New TODO item: defcfun compiler macros M ./TODO +3 Wed Feb 15 16:25:59 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Implement compiler macros for %MEM-REF and %MEM-SET in LispWorks. - Use FLI:FOREIGN-TYPED-AREF if available and dereferencing a number. - Avoid calling INC-POINTER when the offset is a multiple of the type size allowing direct use of the INDEX argument to FOREIGN-TYPED-AREF. - Fall back to open-coding the call to FLI:DEREFERENCE otherwise. M ./src/cffi-lispworks.lisp +84 Wed Feb 15 15:34:42 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Delete LispWorks/Linux .ufsl files on make clean. M ./Makefile -1 +1 Wed Feb 15 14:15:14 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Use C limits for foreign floats and doubles instead of Lisp's. - Export 'float_min', 'float_max', 'double_min', and 'double_max' from the libtest shared library with the values of FLT_MIN, FLT_MAX, DBL_MIN, and DBL_MAX, respectively. - Use *FLOAT-MIN*, *FLOAT-MAX*, *DOUBLE-MIN*, and *DOUBLE-MAX* as test values for foreign floats/doubles instead of the Lisp constants <foo>-POSITIVE-<bar>-FLOAT. M ./tests/bindings.lisp -1 +9 M ./tests/libtest.c -1 +7 M ./tests/memory.lisp -16 +16 Wed Feb 15 11:43:16 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Oops, fix tests. - MISC-TYPES.BOOLEAN.2 was using the wrong ff name. - MISC-TYPES.EXPAND.* need the expand-* methods defined at macroexpansion-time. M ./tests/misc-types.lisp -5 +6 Wed Feb 15 11:16:31 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Change +REQUIRED-DLL-VERSION+ to *REQUIRED-DLL-VERSION*. M ./tests/bindings.lisp -3 +3 Wed Feb 15 03:13:37 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Remove completed TODO item about building 32 and 64 bit libtest. M ./TODO -2 Wed Feb 15 10:35:51 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * A few more tests - Tests for the new macroexpansion-time type translator interface: MISC-TYPES.EXPAND.[1234] - New tests: DEREF.LONG-LONG and DEREF.UNSIGNED-LONG-LONG. - Tests for mem-ref with non-constant type arguments: DEREF.NONCONST.* - Fix some comments in tests/memory.lisp. - New test: MISC-TYPES.BOOLEAN.2 (accepting typedefs to integer types) M ./tests/libtest.c +3 M ./tests/memory.lisp -16 +140 M ./tests/misc-types.lisp -3 +66 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060215.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

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

15 Feb '06

Tue Feb 14 21:01:52 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Minor test changes - Use long instead of int in the big C functions in libtest.c. - Mark callbacks.bff.[12] as expect failures for a couple of lisps. M ./tests/callbacks.lisp -2 +12 M ./tests/libtest.c -31 +31 Tue Feb 14 20:59:06 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Make (%callback 'non-existant-callback) signal an error - Make %callback signal an error for non-existing callbacks. (allegro, sbcl and openmcl) - Regression test: callbacks.non-existant M ./src/cffi-allegro.lisp -1 +2 M ./src/cffi-openmcl.lisp -1 +2 M ./src/cffi-sbcl.lisp -1 +2 M ./tests/callbacks.lisp +6 Tue Feb 14 20:52:57 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Implement %MEM-REF and %MEM-SET compiler macros for Allegro CL. M ./src/cffi-allegro.lisp +20 Tue Feb 14 20:26:51 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Ignore RETTYPE in Allegro CL %DEFCALLBACK. M ./src/cffi-allegro.lisp +1 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060214.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

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

14 Feb '06

Mon Feb 13 22:29:28 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Fix float varargs promotion. - Convert floats to doubles in foreign-funcall-varargs. Test DEFCFUN.VARARGS.FLOAT now passes. M ./src/functions.lisp -4 +9 Mon Feb 13 22:27:33 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Preliminary random tester. - Push random-tester.lisp. This was used to generate the BFF tests, but is still not automated. - Update respective TODO item. M ./TODO -6 +1 A ./tests/random-tester.lisp Mon Feb 13 21:28:30 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * MORE TESTS - New tests: callbacks.funcall.2, callbacks.bff.[12], defcfun.bff.[12]. - Re-enable defcfun.varargs.double. - Use #'float instead of #'coerce in the defcfun.varargs.* tests. - Fix dll version in libtest.c. M ./tests/callbacks.lisp -2 +136 M ./tests/defcfun.lisp -5 +125 M ./tests/libtest.c -1 +222 Mon Feb 13 18:28:39 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Change defconstant to defparameter in bindings.lisp M ./tests/bindings.lisp -1 +3 Mon Feb 13 18:19:31 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Macroexpansion-time translators - New interface. expand-to-foreign-dyn, expand-to-foreign and expand-from-foreign. - defcfun/foreign-funcall/defcallback/defcvar use this as well as the compiler macros and setf-expanders for mem-ref, mem-aref, and foreign-slot-value. - Also, parse ignore declarations and use them to avoid translating such types (thus avoiding breaking the ignore declaration). M ./src/foreign-vars.lisp -13 +7 M ./src/functions.lisp -46 +44 M ./src/package.lisp -1 +4 M ./src/types.lisp -40 +118 Sun Feb 12 12:27:09 CST 2006 Jack Unrue <jdunrue(a)gmail.com> * Implement simple version check for libtest DLL M ./tests/bindings.lisp +9 M ./tests/libtest.c +2 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060213.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

Re: [cffi-devel] wanted: testsuite .dll
by Hoehle, Joerg-Cyril 14 Feb '06

14 Feb '06

jamesjb(a)jamesjb.com writes: >It would be nice to figure out how to get the ASDF system to compile >the DLL on Windows. That would be a bad idea. Presumably most users of CFFI on MS-Windows don't have MS-VC (or Mingw). But IMHO all users should be entitled to run a testsuite. > I'm not sure I'd want to include the DLL in the >repository as the risk of it not getting updated when the testsuite is >updated is somewhat high [...] IMHO not really a problem, because the .dll will stabilize, while the testsuite will continue to grow. Strict solution: add a version number (foreign-var) to the .dll and check it when loading the testsuite. Then people will know when it is outdated and hope for a new one from the CFFI site. As I said, presumably the .dll will receive seldom updates. Regards, Jorg Hohle.

4 11

Re: [cffi-devel] Optimizing type translators
by Hoehle, Joerg-Cyril 13 Feb '06

13 Feb '06

Luís Oliveira wrote: >So, the idea came up of providing some sort of compiler-macro-like >facility for type translators. I'm happy to see that progress is being made here, although I currently have no time to look at it and give feedback. >As I said, I'm trying to keep this simple, so the way this works now is >that one of these translators completely hijacks the normal >translators. Namely, it wouldn't follow the typedef chain and apply all >translators (what would it use the run-time ones? the >macroexpanion-time ones? I had the feeling that ther was a slight error in the old transformers: the transform-*-FORM should have defaulted to the run-time call to convert-*, but the default was the identity function. The idea is: if there's a compile-time (actually, macro-expand time) optimization, do it; otherwise call run-time converters. >foreign-slot-value (or mem-ref/mem-aref). Would it be a good >idea to use >these translators in the respective compiler macros? The mechanism should be general: if the type is known, handle it. I think that James' :translate-p is the wrong direction, at least, my understanding of it. Who's going to use it? With all theses current dreams about automatic translation via swig, cparse, xyz, are they going to set that flag or not? Can the automated translators actually decide whether to set that flag? Regards, Jörg Höhle.

1 0

[cffi-devel] Optimizing type translators
by Luís Oliveira 12 Feb '06

12 Feb '06

Hello, So, the idea came up of providing some sort of compiler-macro-like facility for type translators. James suggested the interface should look like the run-time translators so here's what I have. (I'm trying to keep it simple). Generic Functions: (macroexpand-type-to-foreign value-form var body type) (macroexpand-type-from-foreign value type) (macroexpand-to-foreign value-form var body type) (macroexpand-from-foreign value-form type) A few questions: - maybe expand-* instead of macroexpand-*? - *-to-foreign, as you can see is the equivalent to the previous :to-c-dynamic translation. Would we want to provide the equivalent of :to-c too? (defmethod macroexpand-to-foreign (value var body (type (eql 'coerce-to-double))) `(let (,var (double ,value)) ,@body)) vs. (defmethod macroexpand-to-foreign (value (type (eql 'coerce-to-double))) `(double ,value)) And then then the dynamic extent version would be called what? (macro)expand-dynamically-to-foreign? As I said, I'm trying to keep this simple, so the way this works now is that one of these translators completely hijacks the normal translators. Namely, it wouldn't follow the typedef chain and apply all translators (what would it use the run-time ones? the macroexpanion-time ones? Also this would make it a bit harder to determine whether a given type has a translator. Right now, what I do is call macroexpansion-{to,from}-foreign and one of the default methods will return 'no-expansion if no method was specialized on the type.) One final question. We can guarantee that these are used in defcfun, foreign-funcall, defcallback. However, we can't make such guarantees for foreign-slot-value (or mem-ref/mem-aref). Would it be a good idea to use these translators in the respective compiler macros? I'm inclined to say yes. Any comments? -- Luís Oliveira luismbo (@) gmail (.) com Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt

1 2

[cffi-devel] Python callback figured out and working
by Jeremy Smith 11 Feb '06

11 Feb '06

Hi, I posted here asking for some help with macros. I also posted to comp.lang.lisp and got a nice reply from Pascal B., so I have it all working now and don't need any further help. CFFI-Devel would probably have been helpful, but I know the moderation is slow sometimes. Cheers, Jeremy.

1 0

[cffi-devel] New patches: 10-Feb-2006
by loliveira＠common-lisp.net 11 Feb '06

11 Feb '06

Fri Feb 10 18:31:23 CST 2006 James Bielman <jamesjb(a)jamesjb.com> * Push CFFI-FEATURES:X86-64 on Allegro/amd64. M ./src/cffi-allegro.lisp +1 Fri Feb 10 16:00:55 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Removed outdated comment from the colorize script. M ./doc/colorize-lisp-examples.lisp -2 +1 Fri Feb 10 13:52:48 CST 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Use slanted instead of italic for VAR in style.css M ./doc/style.css -1 +1 Fri Feb 10 10:05:07 CST 2006 Stephen Compall <scompall(a)nocandysw.com> * use lispcmt for code comments instead of @r - Add ROMANCOMMENTS option to manual. - Change all instances of @r to @lispcmt. M ./doc/cffi-manual.texinfo -47 +55 Thu Feb 9 21:50:38 CST 2006 Stephen Compall <scompall(a)nocandysw.com> * make Texinfo @r and colorize play nice - Comment out master menu entry for explain-foreign-slot-value so manual builds again. - Add @r to all Lisp comments in manual. - (Tutorial-easy_setopt): Revert previous @dots{}; it is literal `...', not an ellipsis. Oops. - In colorize-lisp-examples.lisp, remove the output generated by @r from Lisp blocks. Also shove around the process-file code some. M ./doc/cffi-manual.texinfo -51 +50 M ./doc/colorize-lisp-examples.lisp -33 +60 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060210.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel February 2006