On Wed, Sep 21, 2011 at 1:20 AM, wrote:
> Hi Robert,
>
> Robert Bradshaw wrote:
>>
>> The warning seem correct to me, or is foo actually modifying the
>> values of cya and cyb? (I suppose this could be possible by taking the
>> address of the "passed by reference" arguments, but would seem like a
Hi. I've just reverted to 0.14.1 because 0.15 breaks code that implements a
cpp callback in python. It seems to be a name-mangling problem.
I've attached a short test case that shows the problem. They both compile
fine on 14.1 and 15. But if I try and run the 15 compiled version I get
this:
Trace
Hi all,
The path in cython's error output is insensitive to the cwd where cython in
invoked. It seems to be based on this variable in Cython/Compiler/Main.py:
relative_path_in_code_position_comments = True,
If I understand it right, the path output is relative to module it is in,
instead of re
Hi Robert,
Robert Bradshaw wrote:
The warning seem correct to me, or is foo actually modifying the
values of cya and cyb? (I suppose this could be possible by taking the
address of the "passed by reference" arguments, but would seem like a
*very* poor API design.)
thanks for your fast answer!
On Wed, Sep 21, 2011 at 12:32 AM, wrote:
> Hi,
>
> I got a (misleading) Cython warning from the following code example:
>
>
> cdef extern from "":
> void foo(int &a, int &b)
>
> cdef cyfoo():
> cdef int cya, cyb
> foo(cya, cyb)
> -
Hi,
I got a (misleading) Cython warning from the following code example:
cdef extern from "":
void foo(int &a, int &b)
cdef cyfoo():
cdef int cya, cyb
foo(cya, cyb)
Executing "cython --cplus" produced these messages:
