Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Anyway, it is probably not expected by many users that loading a
module in plperlu makes it available to plperl - I was slightly
surprised myself to see it work and I am probably more aware than
most of perl and plperl subtleties.
I think that is a bug and needs to be fixed. We have the precedent of
pltcl, which uses separate interpreters for pltcl and pltclu for exactly
this reason.
Fair enough.
I am not sure what our release timetable is - and presumably this
should also be backpatched if we regard it as a bug. I won't be able
to do much on this front for the next 2 weeks at least.
There is one other wrinkle, that has just come to my attention courtesy
of [EMAIL PROTECTED] This is what the perlembed man page says:
Now suppose we have more than one interpreter instance running at the
same time. This is feasible, but only if you used the Configure
option
"-Dusemultiplicity" or the options "-Dusethreads -Duseithreads" when
building perl.
Now my local perl (FC5/ia64) has usemultiplicity defined. I am not sure
how common this is.
Perhaps people who use other platforms could look for these flags in the
output of
perl -e 'use Config qw(myconfig config_sh config_vars config_re);
print config_sh();'
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
