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

Re: [RFC] Exposing PL_dirty to perl space

Thread Previous | Thread Next
From:
David Golden
Date:
October 4, 2010 04:48
Subject:
Re: [RFC] Exposing PL_dirty to perl space
Message ID:
AANLkTikgmLjkHmmrfnjnNSoXxid3vzYpKSK=OSz3wCzO@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

Given the confusion (already) about BEGIN, I strongly suggest that the
names of these not reference CHECK/INIT/END to avoid even a hint that
BEGIN blocks (or UNITCHECKS) have anything to do with it.  E.g.:

  - initial interpreter construction
  - initial compile-time
  - post-compile-time
  - pre-run-time
  - run-time
  - post-run-time
  - global destruction

-- David

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