Skip Menu |

This queue is for tickets about the List-Intersperse CPAN distribution.

Report information
The Basics
Id: 121468
Status: new
Priority: 0/
Queue: List-Intersperse

People
Owner: Nobody in particular
Requestors: ifettich [...] netsoft.ro
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Re: List-Intersperse-1.00 (fwd)
Date: Sun, 30 Apr 2017 18:28:14 +0300 (EEST)
To: bug-List-Intersperse [...] rt.cpan.org
From: Iosif Fettich <ifettich [...] netsoft.ro>
Hi there, I'm actually writing not about a bug, but about a possible improvement. I found the code to be [very] slow on bigger files; while looking into it, I found a better way to deal with the matter, and since the new code is about 50 times faster than the old one (at least for the files I've tested with) and giving approx. similar results, I thought it would be worth to include yet another sub to make the faster method available as well. I've tried various ways to contact Tim Ayers, but with no success. I'm unsure how to proceed. Thanks, Iosif Fettich Show quoted text
---------- Forwarded message ---------- Date: Tue, 14 Mar 2017 08:03:44 +0200 (EET) From: Iosif Fettich <ifettich@netsoft.ro> To: John Douglas Porter <johndporter@yahoo.com> Cc: "tayers@bridge.com" <tayers@bridge.com> Subject: Re: List-Intersperse-1.00 (fwd) Hi John,
> Hi, Iosif, I saw your msg on perlmonks; I'm sorry I didn't reply to you > sooner.
No problem with that - but thanks for answering!
> I do not maintain that module.  Tim Ayers gave me credit for helping with the > algorithm, but he is the maintainer of the module. 
Do you maybe have an email of him that would work? I've tried the 3 that I could gather on the Net, but all the references seem to be over 10 years old, so I am not at all sure that any of them is actually in use.
> The CPAN FAQ addresses how to make modifications to someone else's > module:http://www.cpan.org/misc/cpan-faq.html#How_maintain_module > http://www.cpan.org/misc/cpan-faq.html#How_adopt_module > > I think in the case of a module like this, taking over maintainership of the > module may not be necessary;  you could simply upload your own new module, > and note in its documentation that it addresses the same problem space as > these other modules.  It might even be a drop-in replacement. > For further & wider advice & input, I recommend you post on PerlMonks.
Thank you for the hints. I'll check to see what the proper next step should be. Many thanks, Iosif Fettich