G.W. Haywood [EMAIL PROTECTED] wrote:
There have been a few problems reported with 5.6 and I have seen one
or two myself.
Although the problems which I saw were largely the result of slightly
dubious coding practices and were easily fixed, some people had more
serious problems and it's why
Chris Winters [EMAIL PROTECTED] wrote:
I'm not sure how you create your database handles (in a central
location then passed around, or in each handler as you need it), but
in MySQL (as with other databases) you can execute a 'use dbname' to
start using a different database.
FWIW, MySQL is
Surat Singh Bhati [EMAIL PROTECTED] wrote:
Any trick to find out that a given CGI is working under
Apache::PerlRun or Apache::Registry. The $ENV{MOD_PERL} says
that script is working under mod_perl, but it does not says it
is working under Perlrun Registry.
Use caller - at the top of your
Oh ghod, what have I started... :)
I promise not to add footnotes to my messages in future...
/Pete/
we now have (particularly if a script
directory is way down the directory hierarchy), gets round the need for
name mangling, and the real script name is still there in the file field
of stack frames for diagnostic purposes.
Pete Jordan
[1] for my Perl exception package (yes, another one :) which
Matt Sergeant [EMAIL PROTECTED] wrote:
It doesn't seem any different from Error.pm to me, except in syntax.
Maybe you could expand on why/where it is different?
OK, yes, it *is* very similar in principle - I would perhaps have been
better to have added to Graham's code, but I suffer from
Matt Sergeant wrote:
Hmm.. maybe you have an original 5.005 (and no patchlevel) then. I
seriously recommend a perl upgrade. There were bugs there that have since
been fixed, and some of those may lead to your error.
Happens here on Perl 5.005_03, Apache 1.3.6, mod_perl 1.21 all built
locally
