On Sat, Oct 2, 2010 at 17:58, Florian Ragwitz <rafl@debian.org> wrote: > Tim Bunce <Tim.Bunce@pobox.com> writes: > >> On Mon, Sep 27, 2010 at 10:01:18PM -0700, Jan Dubois wrote: >>> >>> So I'm wondering if it would be better to have a more generic >>> ${^STATE} that could also indicate other states beyond global >>> destruction, e.g. inside BEGIN/INIT/CHECK/END blocks, or running >>> during sitecustomize.pl etc. At the application level you can always >>> pass this information yourself, but an interpreter provided state >>> would help generic CPAN modules. However, I've never needed these >>> other states so far, so maybe it is overkill. >> >> NYTProf could certainly make use of this. > > After not liking it initially, I've now been convinced. I like it too. Since your patches don't have docs yet I wrote up something that we might want to include in perlvar.pod in altered form: http://gist.github.com/607990 It shows the value of ${^PHASE} in various phases of compilation and execution. The example could be improved since the value of the $::WHERE variable isn't always accurate (it's set in phase.pl before some stuff in Module.pm finishes)Thread Previous | Thread Next