On Mon, 27 Sep 2010, Florian Ragwitz wrote: > So here comes the patch. I'd be very interested in both comments on > the patch and possible other ideas for exposing this information. I like the global much better than an additional argument to DESTROY. In some ways I would have expected to find this information in $^S, but the way it is already defined it doesn't have a good extension mechanism. 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. Cheers, -JanThread Previous | Thread Next