On Mon, Nov 1, 2010 at 10:55, Chas. Owens <chas.ow...@gmail.com> wrote:
> On Mon, Nov 1, 2010 at 02:14, Florian Ragwitz <r...@debian.org> wrote:
> snip
>> Obviously it needs an entry in perlvar, but I don't think explaining
>> all the details of it there is appropriate. "BEGIN, UNITCHECK, CHECK,
>> INIT and END" in perlmod explains many things related to
>> ${^GLOBAL_PHASE}, but it does so from the perspective of a single
>> module, i.e. one compilation unit, for which most of the behaviour of
>> the new variable is irrelevant, as that's only concert with global
>> phases. Also it'd seem somewhat unlikely that anyone would look up
>> "perlmod - Perl modules (packages and symbol tables)" to read about the
>> phases of the interpreter.
> snip
>
> My gut reaction is that the values need to be documented in perlvar in
> a similar way to how you have listed them here and a mention of it
> should be in each paragraph of perlmod that deals with BEGIN, INIT,
> etc. I will throw something together tonight.
snipI have attached my first draft of the documentation (they include brian d foy's changes from last night). Also attached is a patch that adds a mention of the fact that string do and require behave the same way as string eval with respect to UNIT and INIT blocks. -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read.
0002-add-example-for-GLOBAL_PHASE-and-description-to-perl.patch
Description: Binary data
0001-string-do-and-require-don-t-execute-INIT-and-CHECK-b.patch
Description: Binary data
