develooper Front page | perl.perl5.porters | Postings from September 2010

RE: [RFC] Exposing PL_dirty to perl space

Thread Previous | Thread Next
From:
Jan Dubois
Date:
September 27, 2010 22:01
Subject:
RE: [RFC] Exposing PL_dirty to perl space
Message ID:
057701cb5eca$2ff521f0$8fdf65d0$@activestate.com
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,
-Jan 


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About