On Jul 12, 2004, at 5:12 PM, Stas Bekman wrote:
It does so only for mod_perl itself. It doesn't solve it for CPAN modules.
Yes, but it allows them to solve it themselves:
use constant => MODPERL = eval { require Apache2 } ? 2 : eval { require Apache } ? 1 : die $@;
Right?
Depends on what's your goal. What if you have both installed? You will never get 1.
This patch introduces nothing that you can't easily do without it. The only purpose is to workaround CPAN/PAUSE limitations.
moreover at the moment mp1's Apache is invalid, and for mp2 anything before the next version won't have $Apache2::VERSION at all. So it's probably only after 2.0 is released and we completely deprecated 1.99_xx, you will be able to rely on that. Therefore it's better to continue documenting that one should check $mod_perl::VERSION.
The only drawback I can see is a new potential for confusion: "which module should I require, mod_perl or Apache2", which of course will be documented, but who reads docs nowadays...
Not me! ;-)
Seriously, I think that the gradually improving docs will help. And this sort of thing should definitely go into the FAQ.
99% of the user docs are FAQ. so if you call those docs or FAQ it's exactly the same thing.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
