Hopefully this is done right. As discussed in the parallel thread, I
want to take the pod files from docs/src/api/mod_perl-2.0 and install
them with the rest of .pm files. Once this is done we can truly split
the .pm and .pod.
Notice that this has nothing to do with the documentation build sys
Randy Kobes wrote:
> On Wed, 3 Oct 2001, Stas Bekman wrote:
>
>
>>If I put foo/Makefile.PL into the root of the modperl-2.0, it gets
>>automatically executed with the same args at the top Makefile.PL and all
>>the make calls are automatically propogated there as well, now I cannot
>>figure out
this came to the modperl@ moderator address. :-) If someone wants
to reply it would be nice.
--
ask bjoern hansen, http://ask.netcetera.dk/ !try; do();
-- Forwarded message --
Date: Tue, 2 Oct 2001 10:56:56 EDT
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: re: why?
On Wed, 3 Oct 2001, Stas Bekman wrote:
> If I put foo/Makefile.PL into the root of the modperl-2.0, it gets
> automatically executed with the same args at the top Makefile.PL and all
> the make calls are automatically propogated there as well, now I cannot
> figure out why if I put the Makefile.P
If I put foo/Makefile.PL into the root of the modperl-2.0, it gets
automatically executed with the same args at the top Makefile.PL and all
the make calls are automatically propogated there as well, now I cannot
figure out why if I put the Makefile.PL not on the first level but
somewhat deeper
I've committed the first few documents for the API documentation. Since
nobody has followed up on my post from a few weeks ago. Here is what
I've done:
- The API docs will reside in their own .pod files
- Each sub-project will have its own directory under docs/src/api
Here is an example:
docs
In all XS files we disable prototypes in the boot section, but not in the
rest of the file, which means that by default the prototyping is enabled.
However with a stock 5.6.1 perl the prototypes are missing and therefore
in maintainer mode it won't build. I've even tried to explicitly specify
-pr
Philippe M . Chiasson wrote:
> Right on all counts Stas...
>
> Only unresolved issue left is the malloc stuff
>
> I just't can't figure out how to get my hands on an apr_pool at this time.
> I agree, using malloc if _bad_ , just tell me where can I get a pool from?
There are 2 places mall
> -Original Message-
> From: Philippe M . Chiasson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 02, 2001 3:48 AM
> To: [EMAIL PROTECTED]
> Subject: [Patch] Apache->module()
>
>
> Hi, this patch implements the Apache->module() functionnality
> with a few differences.
>
> Apache
Right on all counts Stas...
Only unresolved issue left is the malloc stuff
I just't can't figure out how to get my hands on an apr_pool at this time.
I agree, using malloc if _bad_ , just tell me where can I get a pool from?
Gozer out.
Index: todo/api.txt
==
Philippe M . Chiasson wrote:
> Hi, this patch implements the Apache->module() functionnality with a few differences.
>
> Apache->module() is in Apache::compat and the real name for this is
>Apache::Module::loaded()
> and I am open for better suggestions. "if (Apache->module('Apache::Auth'))" d
On Mon, Oct 01, 2001 at 02:00:26PM -0600, Bryan T. Schmidt wrote:
> >[snip]
> >
> >>Bryan T. Schmidt wrote:
> >>
> >> This seems funny to me...
> >>
> >> I have Perl 5.6.1, Apache 1.3.17, and mod_perl 2.8.0. I am
> >>
> >
> >wow, that version of mod_perl is up there ;)
> >
> >I know there wer
Hi, this patch implements the Apache->module() functionnality with a few differences.
Apache->module() is in Apache::compat and the real name for this is
Apache::Module::loaded()
and I am open for better suggestions. "if (Apache->module('Apache::Auth'))" doesn't
quite
make as much sense to me
13 matches
Mail list logo
