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

Re: [RFC] Exposing PL_dirty to perl space

Thread Previous | Thread Next
Tim Bunce
October 4, 2010 02:21
Re: [RFC] Exposing PL_dirty to perl space
Message ID:
On Mon, Oct 04, 2010 at 07:40:48AM +0200, Florian Ragwitz wrote:
> However, most of my previous answer still applies. ${^PHASE} provides
> "what's the current global phase of the whole interpreter?", not "did
> the interpreter have to compile some more code after already having
> entered run-time?" or anything like that.
> Phases are executed in the order of the list quoted above. Once in one
> stage, there's no going back.

I know I suggested 'phase' as the name of this concept but I have a
nagging feeling that it'll cause confusion with perl6 'phasors'.
And that'll only get worse as perl6 becomes more widely used.

Also 'phase' seems to me to connote a lightweight 'oscillating' kind of
thing that people could naturally assume relates to BEGIN blocks etc.

The other suggestion I made was 'stage'. That seems to connote a more
'heavyweight' concept and a progression along a sequence in a lifecycle.

So I suggest the variable is renamd to ${^STAGE}.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About