develooper Front page | perl.modules | Postings from February 2002

Redux: Devel::Reloader ==> Modules::Reload::Selective

From:
Chris Thorman
Date:
February 27, 2002 16:51
Subject:
Redux: Devel::Reloader ==> Modules::Reload::Selective
Message ID:
a05101404b8a32ccc43ba@[10.100.101.29]
Hi Joshua and other esteemed modules members,

Please recall the exchange below from back in July 2000:

http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-07/msg00246.html

.... in which I requested to upload a module called Devel::Reloader which was similar to your Module::Reload.  You guys on the list helped me realize that Module::Reload::Force or something would be a better name for my module.

Joshua, you perhaps jokingly suggested renaming your module (Module::Reload) to Module::Autoreload presumably so that mine could take the name of yours, which was a kind gesture, but obviously not practical or helpful to those already using your module.

Anyway, eventually there seemed to be no particular further interest in the thread -- see: 

http://www.xray.mpe.mpg.de/cgi-bin/w3glimpse/modules?query=reloader&errors=0&case=on&maxfiles=100&maxlines=30

.... and I got busy and never uploaded anything.

Anyway, I'm finally ready to make this module available.

Considering the discussions that were had, I would be happy to rename my module Module::Reload::Selective or some such similar.

If there are no objections, I'll consider that I have tacit approval to do so and will prepare to package it accordingly and upload (I already have a PAUSE ID).

Sincerely,

-chris

Re: May I put Devel::Reloader into Devel::?
------------------------------------------------------------------------

*	From: Joshua N Pritikin <joshua.pritikin@db.com>
*	To: cthorman@innx.com
*	Cc: modules@perl.org
*	Date: Fri, 28 Jul 2000 20:29:42 -0400
*	Message-ID: <20000728202942.A14792@ghostwheel.wks.na.deuba.com>

------------------------------------------------------------------------


On Fri, Jul 28, 2000 at 02:01:13PM -0700, cthorman@innx.com wrote:
> I feel dumb for not having found that one in CPAN before writing mine :-).

Oops :-)

> Yes, I think mine could maybe be a replacement, BUT it doesn't do the
> one feature that yours does: namely, reload based on file-changed-time.

Hm hm.

> That's an optimization that's probably missing from mine, but I
> intentionally didn't add that because some modules have load-time side
> effects (such as BEGIN blocks) and so forcing an unconditional reload is
> slightly different from reloading only changed files.

Agreed.

> In light of that, maybe mine should be a different module, maybe called:
> 
> Module::Reload::Force

Or maybe I should rename mine to Module::Autoreload?

> .... but one of the biggest aspects of mine is its ability to do
> nothing during end-user runtime, but kick in selectively at Development
> time -- i.e. it doesn't always force the Reload.  That's why I thought
> Devel:: might be the best place for it.

do_stuff() if $ENV{TESTING};  # pretty trival

> I think naming is very important and I
> do want to come up with the best name.

Oh good.  Me too.
-- 

------------------------------------------------------------------------
Chris Thorman                                       (413) 473-0853 e-fax
------------------------------------------------------------------------



nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About