Hi Juanjo.
Sorry for my misunderstanding!
So concerning the simple C++ example I gave before in this thread, which
FFI version do you advice me to use?
ECL's own interface, CFFI, UFFI?
Which one is easier to use for wrapping a whole C++ API?
Which one would result in the faster code?
Blender 3D generates their Python API mostly automatically from the C and
C++ sources. Is something like this thinkable with ECL?
How would I have to proceed?
Thank you very much for your hard work on ECL,
Dietrich
On Sat, Jun 8, 2013 at 11:41 AM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@gmail.com> wrote:
>
> On Thu, Jun 6, 2013 at 10:12 PM, Dietrich Bollmann <dietr...@formgames.org
> > wrote:
>
>>
>> If this impression is wrong, please correct me!
>>
>>
> Well, the impression is probably wrong: all FFIs are intended to work on
> all platforms, provided the right compilers are active and available. As I
> mentioned on a separate thread, I am not aware of the Windows problem -- I
> still have not had time to sit down and reproduce the apparent bug on ffi,
> but this is not a feature nor a design.
>
>
> --
> Instituto de Física Fundamental, CSIC
> c/ Serrano, 113b, Madrid 28006 (Spain)
> http://juanjose.garciaripoll.googlepages.com
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
