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

Re: [RFC] Exposing PL_dirty to perl space

Thread Previous | Thread Next
From:
Eric Brine
Date:
October 3, 2010 22:23
Subject:
Re: [RFC] Exposing PL_dirty to perl space
Message ID:
AANLkTimS1Ze4W28F+y7aM36ZCofkrB++nHO-Y5sd8PwL@mail.gmail.com
On Sat, Oct 2, 2010 at 1:58 PM, Florian Ragwitz <rafl@debian.org> wrote:

> This very much makes sense to me, and I've implemented a ${^PHASE}
> global allowing to differentiate between these phases:
>
>  - initial interpreter construction
>  - initial compile-time
>  - running CHECK blocks
>  - running INIT blocks
>  - run-time
>  - running END blocks
>  - global destruction
>

BEGIN { $SIG{__WARN__} = sub { ... }; } 123; print 456;

If the above occurred in a module, your scheme would report run-time in the
callback were the module required then. I would like the handler to know it
was called by the compiler.

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