-Original Message-
From: Geoffrey Young [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 25, 2001 8:55 AM
To: 'Doug MacEachern'; Stas Bekman
Cc: modperl-2.0 dev-list
Subject: RE: Apache2:: namespace, prerequisite checking and
CPAN listing
oh, I forgot to mention that I know we can
-Original Message-
From: Ken Williams [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 25, 2001 11:06 AM
To: Geoffrey Young
Cc: modperl-2.0 dev-list
Subject: RE: Apache2:: namespace, prerequisite checking and
CPAN listing
[snip]
It should be sufficient to do:
use mod_perl
On Fri, 25 May 2001, Geoffrey Young wrote:
-Original Message-
From: Ken Williams [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 25, 2001 11:06 AM
To: Geoffrey Young
Cc: modperl-2.0 dev-list
Subject: RE: Apache2:: namespace, prerequisite checking and
CPAN listing
[snip
-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 25, 2001 11:26 AM
To: Geoffrey Young
Cc: 'Ken Williams'; modperl-2.0 dev-list
Subject: RE: Apache2:: namespace, prerequisite checking and
CPAN listing
[snip]
use mod_perl 2;
use mod_perl 1
On Fri, 25 May 2001, Ken Williams wrote:
[EMAIL PROTECTED] (Stas Bekman) wrote:
It should be sufficient to do:
use mod_perl;
BEGIN { die horribly if $mod_perl::VERSION = 2 }
It's very handy to remember that 'use' is just 'require' and
'import' in a 'BEGIN' block.
I
what should 'no mod_perl 2.0' todo?
die if $mod_perl::VERSION = 2.0 ?
just something like
$ perl -e no mod_perl 2.0
mod_perl version 2.0 too high--this is version 1.2501 at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
was all I had in mind...
--Geoff
I'm going to talk about 3 issues here: namespace, prerequisite and CPAN
listing. All related to a single issue, a smooth move into the next
generation of mod_perl with as little confusion created as possible.
=head1 namespace
I think we've discussed this slightly before, but I wonder whether
