dougm 00/04/14 18:43:18
Modified:lib/ModPerl Code.pm
src/modules/perl modperl_log.c
Log:
generate MP_TRACE_OPTS
Revision ChangesPath
1.5 +3 -0 modperl-2.0/lib/ModPerl/Code.pm
Index: Code.pm
==
dougm 00/04/14 18:38:46
Modified:lib/ModPerl Code.pm
src/modules/perl .cvsignore mod_perl.c mod_perl.h
modperl_interp.c
Log:
integrate with tracing
Revision ChangesPath
1.4 +35 -2 modperl-2.0/lib/ModPerl/Code.pm
Ind
dougm 00/04/14 18:38:24
Added: src/modules/perl modperl_log.c modperl_log.h
Log:
get tracing stuff in place
Revision ChangesPath
1.1 modperl-2.0/src/modules/perl/modperl_log.c
Index: modperl_log.c
==
dougm 00/04/14 16:52:56
Modified:.Makefile.PL
lib/ModPerl Code.pm
src/modules/perl mod_perl.c mod_perl.h modperl_callback.h
modperl_config.h modperl_types.h
Log:
change from ap_context_t to ap_pool_t
integrate/test in
dougm 00/04/14 16:51:59
Added: src/modules/perl modperl_interp.c modperl_interp.h
Log:
first stab at interpreter pool
Revision ChangesPath
1.1 modperl-2.0/src/modules/perl/modperl_interp.c
Index: modperl_interp.c
==
dougm 00/04/14 16:29:46
Added: lib/Apache .cvsignore
Log:
ignore
Revision ChangesPath
1.1 modperl-2.0/lib/Apache/.cvsignore
Index: .cvsignore
===
BuildConfig.pm
dougm 00/04/14 16:29:12
Added: src/modules/perl .cvsignore
Log:
ignore
Revision ChangesPath
1.1 modperl-2.0/src/modules/perl/.cvsignore
Index: .cvsignore
===
modperl_hooks.h
m
> I don't want to get involved in an unproductive semi-religious war or
> anything
so then why did you?
>, but I'd just like to caution against change for (what seems
> little more than) the sake of change.
re-read my message, it is for more than the sake of change.
> I think it was our Lord
Hi All,
> On Fri, 14 Apr 2000, Stas Bekman wrote:
>
> > > It seems that TIMTOWTDI is going to die soon as everybody tells
> > > me that I should code as shown in "OO Perl" and ""Algorithms
> > > with Perl" :(
>
> On Fri, 14 Apr 2000, Doug MacEachern wrote:
>
> > i'm using '' vs. "" because '' i
On Fri, 14 Apr 2000, Doug MacEachern wrote:
> > > Orwant and friends in "Algorithms with Perl" page 28 claims the first form
> > > is slower.
>
> faster to *parse*, not faster to *run*. stas, your benchmarks don't test
> parse time.
>
> > It seems that TIMTOWTDI is going to die soon as everyb
> > Orwant and friends in "Algorithms with Perl" page 28 claims the first form
> > is slower.
faster to *parse*, not faster to *run*. stas, your benchmarks don't test
parse time.
> It seems that TIMTOWTDI is going to die soon as everybody tells me that I
> should code as shown in "OO Perl" and
On Fri, 14 Apr 2000, Bill Moseley wrote:
> At 11:56 AM 04/14/00 +0300, Stas Bekman wrote:
> >> sticking to the convention of single quoting constant strings
> >
> >Why? You lose the interpolation feature when you need it and you get to
> >the awkward statement like this:
> >
> >> -pri
At 11:56 AM 04/14/00 +0300, Stas Bekman wrote:
>> sticking to the convention of single quoting constant strings
>
>Why? You lose the interpolation feature when you need it and you get to
>the awkward statement like this:
>
>> -print $h_fh "\n#define ",
>> +print $h_fh "\n", '
richter 00/04/14 05:28:40
Modified:embperl CVS.pod.1.html CVS.pod.cont.html Changes.pod.1.html
Changes.pod.10.html Changes.pod.11.html
Changes.pod.12.html Changes.pod.13.html
Changes.pod.14.html Changes.pod.15.html
On 14 Apr 2000 [EMAIL PROTECTED] wrote:
> dougm 00/04/13 21:09:26
>
> Modified:.Makefile.PL
>lib/Apache Build.pm
>lib/ModPerl Code.pm
> Log:
> sticking to the convention of single quoting constant strings
Why? You lose the interpolation fe
> I only set the remoteip if the real ip address is 127.0.0.1.
Ah, but of course. All is well then.
--
Eric
16 matches
Mail list logo
