Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-05-01 Thread Stas Boukarev
Luís Oliveira luis...@gmail.com writes: On Mon, Apr 30, 2012 at 11:02 PM, Max Mikhanosha m...@openchat.com wrote: This fixes it for me (defmethod foreign-type-size ((type symbol))  (let ((*parse-bare-structs-as-pointers* nil))    (foreign-type-size (parse-type type Thanks everyone for

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-05-01 Thread Liam Healy
On Tue, May 1, 2012 at 7:13 AM, Luís Oliveira luis...@gmail.com wrote: On Tue, May 1, 2012 at 7:20 AM, Stas Boukarev stass...@gmail.com wrote: Commonqt seems to work fine now. When will there be a new release with this fix? So that it can be appear in the next quicklisp update. The

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-05-01 Thread Luís Oliveira
On Tue, May 1, 2012 at 9:29 PM, Liam Healy l...@healy.washington.dc.us wrote: I assume this question was about the fix to master, i.e., including cffi-libffi.  I hope that pretty soon (with errors confirmed fixed) this will be tagged as a new release (1.0.0) and QL will pick it up on the next

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-30 Thread Stelian Ionescu
On Thu, 2012-04-19 at 14:46 +, Stas Boukarev wrote: Luís Oliveira luismbo at gmail.com writes: On Thu, Apr 19, 2012 at 2:50 PM, Stelian Ionescu sionescu at cddr.org wrote: (with-foreign-object (p '(:struct timespec) 2) (mem-aref p '(:struct timespec) 1)) In order not to

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-30 Thread Stas Boukarev
Stelian Ionescu sione...@cddr.org writes: On Thu, 2012-04-19 at 14:46 +, Stas Boukarev wrote: Luís Oliveira luismbo at gmail.com writes: On Thu, Apr 19, 2012 at 2:50 PM, Stelian Ionescu sionescu at cddr.org wrote: (with-foreign-object (p '(:struct timespec) 2) (mem-aref p

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-30 Thread Stas Boukarev
Stas Boukarev stass...@gmail.com writes: Stelian Ionescu sione...@cddr.org writes: On Thu, 2012-04-19 at 14:46 +, Stas Boukarev wrote: Luís Oliveira luismbo at gmail.com writes: On Thu, Apr 19, 2012 at 2:50 PM, Stelian Ionescu sionescu at cddr.org wrote: (with-foreign-object

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-30 Thread Stelian Ionescu
On Tue, 2012-05-01 at 00:00 +0400, Stas Boukarev wrote: Stas Boukarev stass...@gmail.com writes: Stelian Ionescu sione...@cddr.org writes: On Thu, 2012-04-19 at 14:46 +, Stas Boukarev wrote: Luís Oliveira luismbo at gmail.com writes: On Thu, Apr 19, 2012 at 2:50 PM,

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-30 Thread Luís Oliveira
On Mon, Apr 30, 2012 at 11:02 PM, Max Mikhanosha m...@openchat.com wrote: This fixes it for me (defmethod foreign-type-size ((type symbol))  (let ((*parse-bare-structs-as-pointers* nil))    (foreign-type-size (parse-type type Thanks everyone for digging into this. While this fix does

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-19 Thread Stelian Ionescu
On Sat, 2012-04-14 at 15:13 -0400, Liam Healy wrote: The system cffi-libffi allows calling functions with structures passed and returned by value. The cffi-libffi branch has been merged into master. Because bare structure reference is deprecated, the merge affects a lot code using CFFI, not

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-19 Thread Liam Healy
IMO the change to mem-aref is bad and will break a lot of code. Until now the contract of mem-aref was that it received a pointer to an array of the referenced type and returned a pointer offset into the array. The fact that it now returns a list is a gratuitous change, with no utility. If we

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-19 Thread Luís Oliveira
On Thu, Apr 19, 2012 at 11:34 AM, Stelian Ionescu sione...@cddr.org wrote: IMO the change to mem-aref is bad and will break a lot of code. Until now the contract of mem-aref was that it received a pointer to an array of the referenced type and returned a pointer offset into the array. The fact

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-19 Thread Stelian Ionescu
On Thu, 2012-04-19 at 14:37 +0100, Luís Oliveira wrote: On Thu, Apr 19, 2012 at 11:34 AM, Stelian Ionescu sione...@cddr.org wrote: IMO the change to mem-aref is bad and will break a lot of code. Until now the contract of mem-aref was that it received a pointer to an array of the referenced

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-19 Thread Liam Healy
On Thu, Apr 19, 2012 at 9:50 AM, Stelian Ionescu sione...@cddr.org wrote: On Thu, 2012-04-19 at 14:37 +0100, Luís Oliveira wrote: On Thu, Apr 19, 2012 at 11:34 AM, Stelian Ionescu sione...@cddr.org wrote: IMO the change to mem-aref is bad and will break a lot of code. Until now the

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-15 Thread Luís Oliveira
On Apr 15, 2012 9:39 AM, Attila Lendvai attila.lend...@gmail.com wrote: let me voice my support here for making cffi better even by introducing some non 100% backwards compatible changes. These changes *should* be backwards compatible though. :-) -- Luís Oliveira http://r42.eu/~luis

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-15 Thread Liam Healy
On Sun, Apr 15, 2012 at 1:31 PM, Attila Lendvai attila.lend...@gmail.comwrote: let me voice my support here for making cffi better even by introducing some non 100% backwards compatible changes. These changes *should* be backwards compatible though. :-) oh well. but still, you get the

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-15 Thread Robert Goldman
On 4/15/12 Apr 15 -3:38 AM, Attila Lendvai wrote: returned by value. The cffi-libffi branch has been merged into master. Because bare structure reference is deprecated, the merge affects a lot code using CFFI, not just those calling functions with structures by value. because so many people

Re: [cffi-devel] Next release of CFFI with cffi-libffi

2012-04-14 Thread Liam Healy
There is a separate system cffi-libffi which needs libffi. You may choose not to load it. However, there are changes to cffi itself as well, which is why testing even without using libffi is a good idea. On Sat, Apr 14, 2012 at 3:24 PM, Kalyanov Dmitry kalyanov.dmi...@gmail.comwrote: On Sat,