On Thu, Mar 29, 2012 at 5:25 PM, David Malcolm wrote:
> On Thu, 2012-03-29 at 11:10 +0100, mark florisson wrote:
>> > Then what happens if you have
>> >
>> > #ifdef FOO
>> > #define BAR 3
>> > #else
>> > #define BAR 4
>> > #endif
>> >
>> > ?? I'm not saying it is hard, but perhaps no longer comple
o that Cython could call it? If so, go for it!
> >
> > (Fortran is actually very much in use in the Cython userbase and would get a
> > lot more "customers" than Go, but if you have more of a CS background or
> > similar I can see why you wouldn't be so inter
Are you all aware of CWrap? It goes a long way to generating pxd files for
a C libary. It can, for example, generate valid pxd files for the whole of
the Intel IPP library.
This would likely be a good launching point for a GSOC project, unless you
really want to start from scratch.
https://github
On 29 March 2012 04:28, Dag Sverre Seljebotn wrote:
> On 03/28/2012 07:58 PM, Philip Herron wrote:
>>
>> Hey all
>>
>> I am implemented a very crude and simplistic and very badly programmed
>> version of a pxd generator i think i understand what were after now
>> but i would appreciate if you look
On Thu, Mar 29, 2012 at 2:25 AM, Stefan Behnel wrote:
> Robert Bradshaw, 29.03.2012 11:19:
On 27 March 2012 17:20, Stefan Behnel wrote:
> the NumPy related tests use a file "numpy_common.pxi" that contains this
> useless code:
>
> """
> cdef extern from *:
> bint FAL
Robert Bradshaw, 29.03.2012 11:19:
>>> On 27 March 2012 17:20, Stefan Behnel wrote:
the NumPy related tests use a file "numpy_common.pxi" that contains this
useless code:
"""
cdef extern from *:
bint FALSE "0"
void import_array()
void import_umath()
>>>
On Tue, Mar 27, 2012 at 11:49 PM, Stefan Behnel wrote:
> Lisandro Dalcin, 27.03.2012 21:34:
>> On 27 March 2012 17:20, Stefan Behnel wrote:
>>> the NumPy related tests use a file "numpy_common.pxi" that contains this
>>> useless code:
>>>
>>> """
>>> cdef extern from *:
>>> bint FALSE "0"
>>>
