Date: Fri, 16 Jan 2004 13:54:04 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Sergey Matveychuk <sem@ciam.ru> Cc: Mike Harding <mvh@ix.netcom.com> Subject: Re: perl 5.8 and malloc (and mod_perl) Message-ID: <20040116135404.50f290f2@Magellan.Leidinger.net> In-Reply-To: <4007D8C6.1030703@ciam.ru> References: <20040115233128.BE39954E5@netcom1.netcom.com> <20040116122858.278c2527@Magellan.Leidinger.net> <4007D8C6.1030703@ciam.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Jan 2004 15:27:50 +0300
Sergey Matveychuk <sem@ciam.ru> wrote:
> Alexander Leidinger wrote:
> > I don't know if the situation changed with perl 5.8, but with 5.6 you
> > have to compile with perls malloc if your application makes use of
>
> From lang/perl5.8/Makefile:
> .if defined(WITHOUT_PERL_MALLOC)
> .undef WITH_PERL_MALLOC
> .else
> WITH_PERL_MALLOC= yes
> .endif
>
> WITH_PERL_MALLOC is default.
Yes, I know. I was referring to the implementation of signal handlers in
perl, not to being perl malloc the default in our perl 5.8 or not. I
don't think this situation has changed, as I can't think of an
implementation which gets it right without disallowing certain perl
language constructs in signal handlers, but I there are people out there
which are smarter than I am, and I don't want to limit their creativity
by saying it's not possible...
Just a little note: what if a perl application makes use of signal
handlers and at the same time needs a perl without perl malloc...
Bye,
Alexander.
--
I will be available to get hired in April 2004.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040116135404.50f290f2>