cffi-devel May 2006

cffi-devel@common-lisp.net

14 participants
24 discussions

[cffi-devel] :ensure-float? Was I dreaming?
by Ken Tilton 17 May '06

17 May '06

Yo, dawgs! Lissen up... sorry, too much American Idol. Here's the deal. One of my bindings was not working because the parameter was float and I was passing a fixnum. Coerced to a float and all was groovy. Two things: 1. Minor question: I coulda swore the first time I fixed this I dug around and discovered :ensure-float and used that in my DEFCFUN. The second time I ran into it I went looking for :ensure-float and could not find it. Found :ensure-XXX for a couple other things in the UFFI-compat bit. Maybe it was one of the XXXs. No big. 2. Am I missing something? Is there some reason we cannot have an ensure-float? Is it one of those deals where for some obscure reason unbeknownst to me there is no reliable way to guess what is needed and programmers need to Just Provide the Right Type? thx, kenny

2 1

Re: [cffi-devel] :ensure-float? Was I dreaming?
by Ken Tilton 17 May '06

17 May '06

> Am 17.05.2006 um 21:24 schrieb Ken Tilton: > > > Yo, dawgs! Lissen up... sorry, too much American Idol. > > > > > > Here's the deal. One of my bindings was not working because the > > parameter was float and I was passing a fixnum. Coerced to a float > > and all was groovy. Two things: > > > > 1. Minor question: I coulda swore the first time I fixed this I dug > > around and discovered :ensure-float and used that in my DEFCFUN. > > The second time I ran into it I went looking for :ensure-float and > > could not find it. Found :ensure-XXX for a couple other things in > > the UFFI-compat bit. Maybe it was one of the XXXs. No big. Thx, Frank. But I try to resolve such tears in the space-time continuum before continuing because it often means I missed Something Important. Not this time: found ensure-float as part of the renegade cl-opengl package, which I did use on the Celtk Gears demo. whew! Meanwhile, OT, cl-openal is alive and well and working atop CFFI, via my Hello-CFFI package. I do believe it is Snack time. :) kenny

1 0

[cffi-devel] cffi_0.9.1 vs cffi-060417
by Rick Taube 16 May '06

16 May '06

I have a program that runs well in cffi-060417 (SBCL 0.9.10/linux and openmcl/darwin), but crashes in the 0.9.1 release in SBCL 0.9.10/linux The error message is: vicious metacircle: The computation of an effective method of #<STANDARD-GENERIC-FUNCTION CFFI:FREE-TRANSLATED-OBJECT (3)> for arguments of types (#<BUILT-IN-CLASS T> #<BUILT-IN-CLASS SYMBOL> #<BUILT-IN-CLASS T>) uses the effective method being computed. unfortunately I have no idea what is causing this error other than its happening under my scheduler's callback into lisp. any help trying to figure this out would be appreciated! --rick * (rts) ; RTS running * (sprout (process repeat 5 output (new midi :keynum (between 60 80)) wait .5)) debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread" {A68D371}>: vicious metacircle: The computation of an effective method of #<STANDARD-GENERIC-FUNCTION CFFI:FREE-TRANSLATED-OBJECT (3)> for arguments of types (#<BUILT-IN-CLASS T> #<BUILT-IN-CLASS SYMBOL> #<BUILT-IN-CLASS T>) uses the effective method being computed. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT-RTS ] Abort RTS, stopping scheduler. 1: [CONTINUE-RTS ] Delete current entry and continue. 2: [FLUSH-QUEUE ] Flush pending events from scheduler. 3: [REMOVE-CALLBACK] Remove callback function. 4: [ABORT ] Exit debugger, returning to top level. (SB-PCL::BREAK-VICIOUS-METACIRCLE #<STANDARD-GENERIC-FUNCTION CFFI:FREE-TRANSLATED-OBJECT (3)> (#<BUILT-IN-CLASS T> #<BUILT-IN-CLASS SYMBOL> #<BUILT-IN-CLASS T>) #S(SB-PCL::ARG-INFO :ARG-INFO-LAMBDA-LIST (CFFI::VALUE CFFI::NAME CFFI::PARAM) :ARG-INFO-PRECEDENCE (0 1 2) :ARG-INFO-METATYPES (T CLASS T) :ARG-INFO-NUMBER-OPTIONAL 0 :ARG-INFO-KEY/REST-P NIL :ARG-INFO-KEYS NIL :GF-INFO-SIMPLE-ACCESSOR-TYPE NIL :GF-PRECOMPUTE-DFUN-AND-EMF-P NIL :GF-INFO-STATIC-C-A-M-EMF #S(SB-PCL::FAST-METHOD-CALL :FUNCTION # :PV-CELL NIL :NEXT-METHOD-CALL NIL :ARG-INFO (2)) :GF-INFO-C-A-M-EMF-STD-P T :GF-INFO-FAST-MF-P T)) 0] debugger invoked on a SB-KERNEL::MEMORY-FAULT-ERROR in thread #<THREAD "initial thread" {A68D371}>: memory fault Segmentation fault -bash-3.00$

1 0

[cffi-devel] defcallback ignores ignorable <g>
by Ken Tilton 15 May '06

15 May '06

Whoa, CFFI rocks, having a lot of fun creating an FFI-based version of Celtk. As the subject suggests, methinks the defcallback macro knows about IGNORE but not IGNORABLE. I use the latter a lot because of debug statements that come and go. best, kenny

3 4

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

15 May '06

Sun May 14 19:42:18 EDT 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Fix problem with declarations in DEFCALLBACKs - Place declarations after the translations take place. - We no longer poke at ignore declarations in defcallback. M ./src/functions.lisp -22 +8 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060514.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

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

13 May '06

Fri May 12 11:38:32 EDT 2006 Stephen Compall <scompall(a)nocandysw.com> * change first automatic defbitfield value to 1 - make-foreign-bitfield now starts implicit bitfield values at 1. No more special cases for zero. - Document and update bf tests to match. M ./doc/cffi-manual.texinfo -6 +7 M ./src/enum.lisp -12 +11 M ./tests/enum.lisp -8 +8 Thu May 11 12:22:02 EDT 2006 Stephen Compall <scompall(a)nocandysw.com> * defbitfield: explicit initial zero case - Provide for counting an initial zero as a pseudo-single-bit. - Test bitfield.4. M ./src/enum.lisp -2 +2 M ./tests/enum.lisp +9 Thu May 11 11:42:21 EDT 2006 Stephen Compall <scompall(a)nocandysw.com> * only single-bits affect defbitfield implicit values - Remove a case in which a non-single-bit like 3 could hijack the implicit value computation for defbitfield. - New test bitfield.3 for this behavior. M ./src/enum.lisp -1 +2 M ./tests/enum.lisp +18 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060512.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] implicit defbitfield symbol values
by Stephen Compall 12 May '06

12 May '06

Saw this was documented but not implemented.... http://scompall.nocandysw.com/cffi/implicit-defbitfield-values.darcs.patch Thu May 11 02:21:06 CDT 2006 Stephen Compall <scompall(a)nocandysw.com> * implicit defbitfield symbol values - Foreign Type Translators: defctype does not create Lisp types; you have to use eql specializers. - enum.lisp: Use reduce in %foreign-bitfield-value. Code a default rule for bitfield symbol values. -- Stephen Compall http://scompall.nocandysw.com/blog

3 5

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

12 May '06

Thu May 11 10:50:35 EDT 2006 Luis Oliveira <loliveira(a)common-lisp.net> * Fix defbitfield bug and new test - Bug fix: when the first value was provided a (< foo nil) comparision would occur. Regresion test: bitfield.1. - New test bitfield.2. M ./src/enum.lisp -5 +5 M ./tests/enum.lisp +23 Thu May 11 03:21:06 EDT 2006 Stephen Compall <scompall(a)nocandysw.com> * implicit defbitfield symbol values - Foreign Type Translators: defctype does not create Lisp types; you have to use eql specializers. - enum.lisp: Use reduce in %foreign-bitfield-value. Code a default rule for bitfield symbol values. M ./doc/cffi-manual.texinfo -25 +32 M ./src/enum.lisp -11 +20 M ./src/utils.lisp -1 +11 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060511.tar.gz Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi;a=summary

1 0

[cffi-devel] Calculating size of C struct .?!
by Frank Goenninger 10 May '06

10 May '06

Hi again ;-) I do have the following C struct: typedef unsigned long tcflag_t; typedef unsigned char cc_t; typedef long speed_t; /* XXX should be unsigned long */ struct termios { tcflag_t c_iflag; /* input flags */ tcflag_t c_oflag; /* output flags */ tcflag_t c_cflag; /* control flags */ tcflag_t c_lflag; /* local flags */ cc_t c_cc[NCCS]; /* control chars */ speed_t c_ispeed; /* input speed */ speed_t c_ospeed; /* output speed */ }; with NCCS being #define'd to 20. I need to allocate space for this struct and therefore want to know its size ... As I don't need the struct itself I thought about calculating the size but I figure there's the problem of getting all the padding to count to the size... How would I do that ? Thx!! Frank

2 2

[cffi-devel] New patches: 6-May-2006
by loliveira＠common-lisp.net 07 May '06

07 May '06

Sat May 6 20:35:11 EDT 2006 James Bielman <jamesjb(a)jamesjb.com> * Make :POINTER a parameterized foreign type. - :POINTER without arguments is a void pointer. - (:POINTER :INT) is a pointer to an :INT. - These nest properly: (:POINTER (:POINTER :INT)). - Pointers are not type checked yet---an optional pointer type checker will be added someday. M ./src/early-types.lisp +44 M ./src/types.lisp -1 +7 M ./tests/defcfun.lisp -5 +5 Sat May 6 20:28:29 EDT 2006 James Bielman <jamesjb(a)jamesjb.com> * Bugfix: Quote type arguments to %DEFCFUN-VARARGS. M ./src/functions.lisp -1 +1 An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-060506.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 May 2006