Thanks Tom, good info I had not come across before! The page refers to
Apache 2, but they must have backported this to Apache 1.3 at some point
as well.
On Mon, 3 Apr 2006, Tom Schindl wrote:
Jonathan Field wrote:
Hi all,
I've noticed that under mod_perl any die() (or croak()) call
be in memory the next time
around so it will be faster than the first run anyways.
Just some food for thought.
Cheers,
Jonathan Field
On Sun, 2 Apr 2006, Perrin Harkins wrote:
On Mon, 2006-04-03 at 10:28 +0800, Foo Ji-Haw wrote:
Perrin Harkins wrote:
Jeff wrote:
Your application simply use
am a bit wary of mucking with signal handlers (even perl internal ones)
across the whole system.
Anyways, thanks for any input. My system info is below.
Jonathan Field
zappos.com
PS - The searchable mailing list archive URL that goes out in the inital
subscription email is no longer valid:
Thanks, all, for the prompt attention. I will update my coding habits
accordingly :)
Cheers
On Wed, 10 Dec 2003, Stas Bekman wrote:
> I've pinged Doug and the final verdict is this:
>
>The print-a-scalar-reference feature is now deprecated. There are
>known bugs when using it and it's n
l/2.8.15 OpenSSL/0.9.7b under
FreeBSD 4.6.2-release. The output of perl -V is below.
Thanks in advance for your time, let me know if you need any further
information!
Jonathan Field
---
--- perl -V output:
Summary of my perl5 (revision 5.0 version 6 subversion 1) configurat
like this.
I am not able to verify that, but if it is a common thing, perhaps it's
the "right" way to detect a perl scalar reference from the other side?
Not that I understand anything about the other side anyways :)
Cheers,
Jonathan Field
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
t.
Thanks for the reminder :)
Jonathan Field
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
Thanks for the info. It all makes some sort of sense :)
Jonathan Field
On Tue, 2 Dec 2003, Rafael Garcia-Suarez wrote:
> Jonathan Field wrote:
> > I was surprised that the "SCALAR(0x8ca70e4)" output was identical on
> > subsequent requests to a child -- indicating to
will look through the performance
guidelines some more, though I think I've already applied them all :)
Thanks for your input!
Jonathan Field
#---
# Benchmark code (hope my logic here is reasonable):
#---
#!/usr/local/b
> I'm not sure what you mean here.
> Note that *variables* are lexically scoped, but not values.
I was surprised that the "SCALAR(0x8ca70e4)" output was identical on
subsequent requests to a child -- indicating to me that the ref (and what
it was refering to) may have survived the request cycle?
scalar and the ref are lexically scoped. One would think
they had been destroyed by then? Any clue as to what causes that? Is
this small leak meaningful enough to worry about?
In the meantime I'll prepare to stop using this feature! Unless of course
you end up fixing it :)
Thanks,
Jonathan
l/2.8.15 OpenSSL/0.9.7b under
FreeBSD 4.6.2-release. The output of perl -V is below.
Thanks in advance for your time, let me know if you need any further
information!
Jonathan Field
---
--- perl -V output:
Summary of my perl5 (revision 5.0 version 6 subversion 1) configurat
12 matches
Mail list logo
