search

pinterface / burgled-batteries

A bridge between Python and Lisp (FFI bindings, etc.)
Other
113 stars 21 forks source link

No object pointers for unknown conversions #1

Closed mmontone closed 10 years ago

mmontone commented 10 years ago

NIL is returned instead of an object pointer for unknown conversions

Example:

BURGLED-BATTERIES> (run "object()") NIL

mmontone commented 10 years ago

If evaluate with run*, I do get the pointer:

BURGLED-BATTERIES> (run* "object()")

.(SB-SYS:INT-SAP #X7FFFF7E4E0A0)

mmontone commented 10 years ago

Ok. If I set (setf python.cffi::unknown-translation-policy :pass-through) then, well, objects are passed through. Now I realize there are more things going on than I understand atm.

pinterface commented 10 years ago

Just in case you're still wondering about this: the reason #'run doesn't return a pointer by default is because handing back pointers to code unprepared to handle them felt unhelpful and seemed likely to be unsafe.

(Apologies for my failure to respond in a timely manner. Apparently github does not send new issue notifications by default.)

mmontone commented 9 years ago

Hi. Just in case you are not receiving notifications from github, I've opened and issue I would like you to look at.

Thanks!

Mariano

On Mon, Nov 17, 2014 at 10:26 PM, pinterface notifications@github.com wrote:

Just in case you're still wondering about this: the reason #'run doesn't return a pointer by default is because handing back pointers to code unprepared to handle them felt unhelpful and seemed likely to be unsafe.

(Apologies for my failure to respond in a timely manner. Apparently github does not send new issue notifications by default.)

— Reply to this email directly or view it on GitHub https://github.com/pinterface/burgled-batteries/issues/1#issuecomment-63408037 .