In perl.git, the branch smoke-me/khw-lexencoding has been created

<http://perl5.git.perl.org/perl.git/commitdiff/029e539ecc5a44eac28817293575c5f5ff1a3823?hp=0000000000000000000000000000000000000000>

        at  029e539ecc5a44eac28817293575c5f5ff1a3823 (commit)

- Log -----------------------------------------------------------------
commit 029e539ecc5a44eac28817293575c5f5ff1a3823
Author: Karl Williamson <[email protected]>
Date:   Tue Nov 18 22:02:21 2014 -0700

    toke.c: Consistently upgrade under encoding
    
    The documentation says that intermixing above-Latin1 code points with
    ones that would be otherwise encoded to something else, like Greek,
    causes the encoding to be foregone.  Until this commit, this only
    happened when the above-latin1 code point came first in the string
    constant being scanned; meaning string-order was important.  This
    changes things to match the documentation

M       cpan/Encode/t/encoding.t
M       toke.c

commit 216d7e7f2c45521c5e47f66ebe2c2aa6249be9a4
Author: Dagfinn Ilmari MannsÃ¥ker <[email protected]>
Date:   Mon Nov 10 23:54:46 2014 +0000

    Deprecate setting ${^ENCODING}
    
    The commiter added a no warnings in t/op/leaky-magic.t, and made other
    minor changes because of rebasing issues.

M       mg.c
M       pod/perldiag.pod
M       pod/perlvar.pod
M       t/lib/warnings/mg
M       t/op/leaky-magic.t
M       t/re/pat_re_eval.t
M       t/uni/chomp.t

commit c5450c71b2cf59d85aba75a3aba9653f1b99dac2
Author: Karl Williamson <[email protected]>
Date:   Tue Nov 18 17:23:54 2014 -0700

    mg.c: White-space only
    
    Indent due to new blocks from previous commit

M       mg.c

commit c19c2c56433c2bb84f2fee066cc24118bde335d7
Author: Karl Williamson <[email protected]>
Date:   Tue Nov 18 17:03:03 2014 -0700

    Make encoding pragma lexical in scope
    
    The encoding pragma is deprecated, but in the meantime it causes spooky
    action at a distance with other modules that it may be combined with.
    In these modules, operations such as chr(), ord(), and utf8::upgrade()
    will suddenly start doing the wrong thing.
    
    The documentation for 'encoding' has said to call it after loading other
    modules, but this may be impractical.  This is especially bad with \N{}
    now, as it auto-loads charnames at first use, which likely is after the
    'encoding'.
    
    There is an issue with combining this with setting the variable
    ${^ENCODING} directly.  The potential for conflicts has always been
    there, and remains.  This commit introduces a shadow hidden variable,
    subservient to ${^ENCODING} (to preserve backwards compatibility) that
    has lexical scope validity.

M       cpan/Encode/encoding.pm
M       embedvar.h
M       gv.c
M       intrpvar.h
M       mg.c
M       perl.h
M       pp_ctl.c
M       sv.c

commit 131490a0ef42e487c7f853cacaa50de96c800b43
Author: Karl Williamson <[email protected]>
Date:   Fri Nov 14 11:18:57 2014 -0700

    Make a function to get PL_encoding's value
    
    This is in preparation for making the retrieval more complex in future
    commits than it is now.  This is going into mg.c because the value is
    magical.

M       embed.fnc
M       embed.h
M       mg.c
M       pad.c
M       pp.c
M       pp_hot.c
M       proto.h
M       regcomp.c
M       sv.c
M       toke.c

commit 51611aeca4b048145cb2071cb58b08833292b577
Author: Karl Williamson <[email protected]>
Date:   Tue Nov 11 22:25:37 2014 -0700

    Make testing for PL_encoding into a macro
    
    This is in preparation for making the test more complicated.

M       pad.c
M       perl.h
M       pp.c
M       pp_hot.c
M       pp_sys.c
M       regcomp.c
M       sv.c
M       toke.c
-----------------------------------------------------------------------

--
Perl5 Master Repository

Reply via email to