Devel::LeakTrace

[Jacqui Caren]

Andy Armstrong wrote:
> The problem with keeping the change to the minimum required in this  
> case is that apart from a bit of boiler plate the module just  
> implements a fairly simple algorithm - and it's the algorithm that  
> doesn't scale. So most of it will have to change.

Which usually takes a while longer for an author to review :-)

It would be NICE if people replied saying thanks for your
patch, I will look at it in ~Feb and should get back to you
Marchish, but it almost never happens.

At least an email like that gives you a chance to send a
timely reminder, without hassling.

>> We currently have four such modules that have elicited negative of  no 
>> response from the author. We keep patches for all of them.
> 
> Uh huh. Well I'll just keep working on it and if I get something  
> decisively better I'll see what happens, thanks :)

I think this is who you are trying to contact?
http://unixbeard.net/~richardc/talks/siesta/richardc.jpeg
He looks a bit like my Paul :-)

The good news is that he is uploading to cpan, so he has not
"gone walkies".
http://cpan.etla.org/authors/id/R/RC/RCLAMP/?C=M;O=A