I believe that if effect is not in sync with the order of occurrence,
it can create confusions. Probably, one possible solution ( and
probably the simplest one ) is to populate %ENV before any
.. block.
I'd be interested in writing the patch for this if required. But it
will be really great to hav
Philippe,
if you have a chance, please take a look at this static build:
make clean && /home/stas/perl/5.6.1/bin/perl Makefile.PL MP_INST_APACHE2=1
MP_GENERATE_XS=1 MP_USE_STATIC=1
MP_AP_PREFIX=/home/stas/apache.org/httpd-2.0/
MP_AP_CONFIGURE="--with-mpm=prefork" MP_DEBUG=1 MP_TRACE=1 MP_USE_GTO
[the previous thread was too long, starting a new one]
*** what methods need to be protected from dependent blocks going out
*** of scope ***
the following looks only at the first level (i.e. methods taking a
pool object):
-
*** returning
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
in fact the only reason modperl_hash_tie calls sv_magic is to assign some
flags, may be it can be eliminated completely. I haven't looked at the other
places where it is used. Why do you think the order matters, if it doesn't
really
