Re: Taking over a module

Perhaps this is an opportunity to reinvent a better wheel.  Start with the
orginal code, include a note of attribution, and then write what you want.

I think you'll want to rename your version, and leave his older version in
place for those people that already use it.  I don't know that it's
"proper" necessarily, but it seems reasonable to me.

I wrote my own Ini class a while ago, because I never could get in touch
with him, and I needed some different functionality.  I left out a lot of
bells and whistles that I didn't need, so mine's a bit smaller.  I'll
always be grateful to him for the "here doc" functionality.  I don't know
why I never thought of it before.

I say, "Have at it." :-)

-Brad

On Fri, 21 Jan 2000, Rich Bowen wrote:
> Thanks. I'd gone down that road about a year ago, but never found him.
> Bummer.
> 
> Rich
> -- 
> http://www.ApacheUnleashed.com/
> Lexington Perl Mongers - http://lexington.pm.org/
> PGP Key - http://www.rcbowen.com/pgp.txt
>