Adam Kennedy <[EMAIL PROTECTED]> writes:
[...]
> What is causing the biggest issue for me, as someone who as a rule
> _never_ gets involved in these kinds of things in public, is that he
> is willing to immediately and completely discount the opinions of
> everyone else, whether or not they are t
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Is parms->pool freed when config phase is over?
Well, AFAIK, parms->pool is process->pconf, and that doesn't get wiped
until the process terminates.
So we need to use a temp pool instead.
Yes, most certainly, and that would have to be parms->temp_pool
Philippe M. Chiasson wrote:
Is parms->pool freed when config phase is over?
Well, AFAIK, parms->pool is process->pconf, and that doesn't get wiped
until the process terminates.
So we need to use a temp pool instead.
Yes, most certainly, and that would have to be parms->temp_pool
Index: src/modul
Randy Kobes wrote:
> As probably with most of you, I'm getting worried with the
> tone of the discussion on the mp2 namespace problem, and the
> directions it's heading - getting locked out of CPAN, etc.
> And, rightly or wrongly, getting a a sizeable fraction of
> the Perl community upset on the e
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Stas Bekman wrote:
[...]
In any case, why the handler is not freed when section is done?
That's a certain _leak_ right there.
Is parms->pool freed when conf
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Stas Bekman wrote:
[...]
I've traced it down to this line :
handler = modperl_handler_new(p, handler_name);
So basically, to be able to use the existing modperl_handler_*
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Stas Bekman wrote:
[...]
I've traced it down to this line :
handler = modperl_handler_new(p, handler_name);
So basically, to be able to use the existing modperl_handler_*
framework to
run sections
Stas Bekman <[EMAIL PROTECTED]> writes:
> Randy Kobes wrote:
> [...]
>> Although this may not be the best time to raise this, the
>> strong opinions being expressed, plus the shortness of time
>> on the part of the many of us, perhaps we could look at what
>> would be involved to move the modules
On Saturday 01 January 2005 10:24 am, Stas Bekman wrote:
> Randy Kobes wrote:
> [...]
> > Putting aside for the moment the relationship of these to
> > their mp1 counterparts, it shouldn't be too hard to come up
> > with alternate, descriptive names, either in an Apache2::*
>
> -1 to embedding num
Pratik wrote:
Looks like this patch is solving all the problems :)
Thanks Pratik, I'll wait till monday before I commit it, in case someone
has an input. And then we can get a new RC out.
Happy New year !
Thanks, Happy New Year.
--
_
Looks like this patch is solving all the problems :)
Happy New year !
Thanks,
Pratik
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Randy Kobes wrote:
[...]
Although this may not be the best time to raise this, the
strong opinions being expressed, plus the shortness of time
on the part of the many of us, perhaps we could look at what
would be involved to move the modules in the mp2 core so as
not to conflict with mp1. If I coun
12 matches
Mail list logo
