Re: Perl 5.6.0 Is Here!
According to Stephen Zander:
> >>>>> "Chip" == Chip Salzenberg <chip@valinux.com> writes:
> Chip> Now the key question: How is Config.pm supposed to know
> Chip> whether it's being called by libperl.so or /usr/bin/perl?
>
> Uh, I missed the begining of this discussion (lost some mail) but: why
> would it need to?
It would need to if Darren packaged a libperl.so with a Perl that
didn't use it. The shared libperl.so would be for the use of e.g. vim
and Apache.
In that case, code inside e.g. mod_perl would need to see
$Config{useshrplib} eq 'true', while code in perl programs executed by
/usr/bin/perl would need to see $Config{useshrplib} eq 'false'.
> I don't see why anything embedding perl in something else (vim,
> apache-perl etc) would want to use a different perl than what the
> user sees everywhere else.
It's not a need it's a want -- Darren wants the main Perl binary not
to suffer the slowdown imposed by a shared libperl.so.
> Donw that path lies madness.
Oh, there we agree.
> Would would be more sensible, IMHO, build bothe the .a & .so (the
> standard build allows this)
It _does_?! I can't find a thing about that anywhere.
--
Chip Salzenberg - a.k.a. - <chip@valinux.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
Reply to: