Amaury Forgeot d'Arc, 20.07.2012 22:28:
> 2012/7/20 Alexander Pyattaev:
>> I think that most of the end-users would not care much and would use SWIG
>> anyway, because it is simple to do and scalable. So whatever API you decide
>> to go with, the only real problem will be to make a swig wrapper lib
2012/7/20 Alexander Pyattaev :
> I think that most of the end-users would not care much and would use SWIG
> anyway, because it is simple to do and scalable. So whatever API you decide
> to go with, the only real problem will be to make a swig wrapper library for
> that and about 80% of application
I think that most of the end-users would not care much and would use SWIG
anyway, because it is simple to do and scalable. So whatever API you decide
to go with, the only real problem will be to make a swig wrapper library
for that and about 80% of applications that use SWIG would not even need
any
Armin Rigo, 14.07.2012 10:35:
> On Tue, Jul 10, 2012 at 7:57 PM, Amaury Forgeot d'Arc wrote:
>> Do you have an idea what this API would look like?
>> Then I can help with the implementation :)
>
> If we want to go down this path without caring for compatibility with
> CPython's C API, but instead
On 07/14/2012 10:35 AM, Armin Rigo wrote:
Hi Amaury,
On Tue, Jul 10, 2012 at 7:57 PM, Amaury Forgeot d'Arc
wrote:
Do you have an idea what this API would look like?
Then I can help with the implementation :)
If we want to go down this path without caring for compatibility with
CPython's C A
Hi Amaury,
On Tue, Jul 10, 2012 at 7:57 PM, Amaury Forgeot d'Arc
wrote:
> Do you have an idea what this API would look like?
> Then I can help with the implementation :)
If we want to go down this path without caring for compatibility with
CPython's C API, but instead focusing on what gives the
