On Mon, Jun 22, 2015 at 3:13 PM Ian Henriksen <
insertinterestingnameh...@gmail.com> wrote:
> On Tue, Feb 17, 2015 at 2:51 AM Ulrich Dobramysl wrote:
>
>> On Fri Feb 13 2015 at 11:07:39 PM Greg Ewing
>> wrote:
>>
>>> Ulrich Dobramysl wrote:
>>>
>>> > Thanks! I haven't figured out how to call hea
On Tue, Feb 17, 2015 at 2:51 AM Ulrich Dobramysl wrote:
> On Fri Feb 13 2015 at 11:07:39 PM Greg Ewing
> wrote:
>
>> Ulrich Dobramysl wrote:
>>
>> > Thanks! I haven't figured out how to call heap allocated objects, as the
>> > code
>> > ---
>> > cdef OperatorTest *t = new OperatorTest()
>> > t()
On Fri Feb 13 2015 at 11:07:39 PM Greg Ewing
wrote:
> Ulrich Dobramysl wrote:
>
> > Thanks! I haven't figured out how to call heap allocated objects, as the
> > code
> > ---
> > cdef OperatorTest *t = new OperatorTest()
> > t()
> > ---
> > is not translatable by Cython.
>
> Have you tried:
>
>
Ulrich Dobramysl wrote:
Thanks! I haven't figured out how to call heap allocated objects, as the
code
---
cdef OperatorTest *t = new OperatorTest()
t()
---
is not translatable by Cython.
Have you tried:
t[0]()
?
A quick and dirty fix for this would be this patch
for NameNode.calculate_
On Fri Feb 13 2015 at 2:23:45 PM Stefan Behnel wrote:
> Ulrich Dobramysl schrieb am 11.02.2015 um 09:56:
> > From what I've been able to work out, the problem seems to be that the
> call
> > to "t()" is treated as a NameNode in ExprNodes.py and not an
> AttributeNode.
> > However, I don't know en
Ulrich Dobramysl schrieb am 11.02.2015 um 09:56:
> I tried to declare an external c++ class that includes an operator()
> function in a pxd file. When I then call a class instance, cython generates
> faulty c++ code. It includes a call to "operator()()", and not a call to
> the instance object. Her
