Re^4: How to keep C variables "alive" between invocations with Inline::C

Could you add a method to your sample please?

I tried adding this method:

Node* insert( Node* root ) {
    warn("insert\n"); // DEBUG
    return root;
}
[download]

But I get the classic: Can't locate object method "insert" via package "Node" at ...

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^4: How to keep C variables "alive" between invocations with Inline::C Download Code

Replies are listed 'Best First'.
Re^5: How to keep C variables "alive" between invocations with Inline::C by ikegami (Patriarch) on Sep 28, 2010 at 01:41 UTC
Works for me. What your build output and your .c? But I've found that it creates a second scalar that points to `root`, so `DESTROY` is now being called twice for the same pointer.	[reply] [d/l] [select]
Re^6: How to keep C variables "alive" between invocations with Inline::C by BrowserUk (Patriarch) on Sep 28, 2010 at 02:16 UTC
Okay. Forget it. Mismatch (case) between package name and struct typedef! <Reveal this spoiler or all in this thread> Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. RIP an inspiration; A true Folk's Guy	[reply] [d/l] [select]