> ---------- Forwarded message ----------
> From: Juan Jose Garcia-Ripoll <juanjose.garciarip...@googlemail.com>
> Date: Sun, Apr 25, 2010 at 2:47 PM
> Subject: ECL specific changes for CFFI
> To: cffi-de...@common-lisp.net
> 
> 
> * At the low level ECL has two different foreign function interfaces: one
> used in the interpreter and relying on an external library (libffi) and
> another one, much simpler, using the C compiler. Right now CFFI was only
> using the former unless it was not available. I provide a patch that chooses
> the interface depending on the use of the code: interpreter or compiled.
> (patch attached).

Hi,

I've found a problem with this change:

The dffi-function-pointer-call function should be put under #+dffi,
or CFFI fails to compile due to the si:call-cfun symbol being missing.
Also, it seems that the #-dffi/#+dffi logic is reversed in the
#-ecl-with-backend branch of produce-function-pointer-call.

Alexander

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list

Reply via email to