httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: libapreq-1.2 release candidate
Date Thu, 01 May 2003 02:06:34 GMT
Stas Bekman wrote:

> I'm thinking whether it's possible to still keep the Apache::Test name.

For example Apache::Test's 'make install' could hunt down Apache/test.pm in 
@INC and delete it and install its own version of Apache/test.pm which will 
still work as before and will be exactly the same as Apache/Test.pm.

The problem is how to prevent from mod_perl 1.x upgrades from overwriting 
this. This certainly could be avoided by fixing the next mod_perl 1.28 
release, but what if someone upgrades from 1.26 to 1.27?

Another possible solution is this:

Move all code from Apache/Test.pm, but its $VERSION to Apache/TestCode.pm. The 
latter will declare 'package Apache::Test'. So you need to require 
Apache/TestCode.pm everywhere, but the rest will work as before. What this 
approach achieves is that you don't have the collision, while you still keep 
on using Apache::Test in your code. Admittedly it's a bit confusing that you 
require Apache::TestCode, but use Apache::Test:: functions.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


Mime
View raw message