-----Original Message-----
From: Sam Tregar [mailto:[EMAIL PROTECTED]] 
Sent: Friday, January 25, 2002 7:50 AM
To: Stanley, Jack
Cc: 'Strahan, Gregory N'; [EMAIL PROTECTED]
Subject: RE: Memory Leakage Problems with Inline::C

On Thu, 24 Jan 2002, Stanley, Jack wrote:

>> Thanks folks - that's the good news, now the bad - same problem with
strings
>> and other objects - maybe the macros need changing? For sure the
>> documentation with bold and underline.

>Right - you'll need to make any SV you push onto the stack mortal or it
>won't be destroyed when it goes out of scope.  Ah, I think.  I'm still
>hoping some Inline::C guru will pop out of the ether and tell me I'm
>wrong.  If I'm right then Inline::C-Cookbook needs revision and
>Inline::C's docs need a new chapter on mortality.

>-sam


There no gurus any more. I enjoyed this mailing list before Xmas but now
nothing seems to happen. Note that I didn't do much myself. We are still
hanging waiting for .44 to show its nose.

I am porting one of my programs to perl and it can't work in pure perl so
Inline was a solution (we still have XS).

So can someone give an approximately viable date for .44 or shall I start
hacking in my corner.

This is not a complain about people not doing work that I should do myself
but I think it's better to say nothing so people don't hang waiting for some
promises to be fulfilled.

If .44 is not coming out soon please let us know.

About the documentation that needs upgrade, The standard answer is "great
idea do it and send us patches" this is the most frustrating, useless,
bloody dumb answer ever read in a mailing list and still it's very common.

So smart-head what's your solution?

The cookbook is not so big. Can someone raise his hand and do it?

No, OK let's share the update. I volunteer to do up to 1/3 of the update.
Someone out there sends me what my bit will be and I will do it.

Nadim




Reply via email to