[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: avoiding copy - Luajit FFI
- From: Fabio Kaminski <fabiokaminski@...>
- Date: Tue, 7 Jun 2011 16:26:57 -0300
On Tue, Jun 7, 2011 at 4:12 PM, Mike Pall <mikelu-1106@mike.de> wrote:
> Duncan Cross wrote:
>> On Tue, Jun 7, 2011 at 7:03 PM, Fabio Kaminski <fabiokaminski@gmail.com> wrote:
>> > but cast from void * to char * give me a new address (pointing to
>> > somewhere else) and not the same pointer:
>>
>> This is incorrect. What you are seeing here, when you print the
>> pointer, is not the value of the pointer itself but of the FFI cdata
>> object that has been allocated to house it.
>
> Well, I guess it's probably confusing. And inconsistent with e.g.
> arrays or structs, where the actual start address of the data is
> shown. 64 bit integers or complex numbers already show their value
> and not the (irrelevant) cdata object address, too.
>
> I've just changed it so tostring(pointer) shows the address the
> pointer points to. Much easier to spot NULL pointers, too.
>
> --Mike
>
>
cool feature!
also can't wait for function callbacks to arrive in a future release.. ;)
thanks
- References:
- avoiding copy - Luajit FFI, Fabio Kaminski
- Re: avoiding copy - Luajit FFI, Justin Cormack
- Re: avoiding copy - Luajit FFI, Fabio Kaminski
- Re: avoiding copy - Luajit FFI, Justin Cormack
- Re: avoiding copy - Luajit FFI, Fabio Kaminski
- Re: avoiding copy - Luajit FFI, Fabio Kaminski
- Re: avoiding copy - Luajit FFI, Peter Cawley
- Re: avoiding copy - Luajit FFI, Fabio Kaminski
- Re: avoiding copy - Luajit FFI, Duncan Cross
- Re: avoiding copy - Luajit FFI, Mike Pall