At Tue, 03 Sep 2002 08:41:19 -0400,
Geoffrey Young wrote:
> >
> > I think it should be in mod_perl core, but at the same time,
> > it's worth CPANizing as it allows you to use this method without
> > mod_perl upgrading.
>
> isn't the result the same as what you would get with this:
>
> my
A couple if people have had problems building mod_perl-1.27 on
Win32 because ModuleConfig.c wasn't generated (when no APACHE_SRC
was specified). John Petrakis <[EMAIL PROTECTED]> tracked this
down to $PERL_DIRECTIVE_HANDLERS in Makefile.PL not being defined
in this instance - the attached diff fix
At 21:47 03.09.2002, Randy Kobes wrote:
>On Tue, 3 Sep 2002, Per Einar Ellefsen wrote:
>
> > At 22:52 02.09.2002, Randy Kobes wrote:
> > "e) The perhaps most interesting namespace protection is provided by the
> > perl symbol table itself. A namespace Foo:: is just a package name and its
> > relat
On Tue, 3 Sep 2002, Per Einar Ellefsen wrote:
> At 22:52 02.09.2002, Randy Kobes wrote:
[ ... ]
> >I was thinking more of the hierarchy, not of the functional
> >grouping. The convention of X::Y::Z being related to X::Y by, eg,
> >using or requiring it or through inheritance is widespread (and
>
Tatsuhiko Miyagawa wrote:
> Here I've made a new mod_perl module which allows you to call
> ap_construct_url() from mod_perl.
>
> http://bulknews.net/lib/archives/Apache-CanonicalName-0.01.tar.gz
>
> Any suggestions welcome, especially regarding to:
>
> * Is naming OK?
>
> * Is it worth CPA
