mymalloc isn't thread safe (rurban)
ExtUtils::ParseXS: Changelog, version bump for dev release

Upgrade the version in ExtUtils::ParseXS to 3.13_01 for a development
release.
filelify shouldn't always escape dots.

Follow-up to a9fac63d75d9222a73fbf511ca58ae1d66cbf9a7.  It turns
out that the CRTL doesn't handle the escapes when the path is in
Unix syntax (even though it requires them in native syntax).

  stat('foo/bar.baz.dir;1')

is ok, but

  stat('foo/bar^.baz.dir;1')

fails.  So skip the escaping if there is a slash anywhere in the
path.
Restore directory extension and version in fileify under EFS.

In df2786654 and 8a5aa89570, the traditional behavior of adding
the .DIR;1 onto a fileified directory spec was removed when
operating under Extended Filename Syntax.  Various scary comments
were added about its being a bug to add a type and version onto
a Unix-style path, but actually the CRTL appears to be perfectly
happy with, for example:

   stat('/foo/bar/baz.dir;1');

and without the extension, the home-grown rmdir() fails in the
case of a directory with no preceding path information.  E.g.,

   rmdir('foo');

was failing because there was no internal translation to foo.dir
before passing it to SYS$ERASE.

Moreover, even if there were something wrong with adding .DIR;1,
it has nothing to do with EFS.
Adjust skip counts in t/op/filetest_t.t.

Follow-up to 8db8f6b697e6f, where new tests were added without
changing the (implicit) skip count of 1.
[perl #21396] documentation error in subs.pm
checkAUTHORS.pl: Add another (old?) address for Juerd
Increase $subs::VERSION to 1.01
fix variable not shared warnings coming from the use statement being executed too early
accidentally used my work email for a commit so add it to checkAuthors.pl
Fix bug #109206: ANCH_MBOL with while /.*/g

We had a fencepost error when ANCH_MBOL was enabled that meant we
did not "see" matches at the end of string. This fixes the problem
and adds tests.
Trim directory extension in pathify under EFS.

When Extened Filename Syntax (EFS) is in effect, 1fe570cc5e24ee
changed the age-old behavior of trimming the directory extension
off a directory filename when the path is in Unix syntax.  EFS
really has nothing to do with the necessity to trim .DIR;1 from
the name, so remove the conditional check for EFS from the
existing code.

This gets three more tests passing under EFS in vms/ext/filespec.t.
Update Compress-Raw-Bzip2 to CPAN version 2.047

  [DELTA]

  2.047 28 January 2012

      * Set minimum Perl version to 5.6
Update Compress-Raw-Zlib to CPAN version 2.047

  [DELTA]

  2.047 28 January 2012

      * Allow flush to be called multiple times without any intermediate
        call to deflate and still return Z_OK.
        In the code below $status was Z_BUF_ERROR before this change.

          $def->flush(...);
          $status = $def->flush(...);

      * Added support for zlibCompileFlags

      * Set minimum Perl version to 5.6
Update IO-Compress to CPAN version 2.047

  [DELTA]

  2.047 28 January 2012

      * Set minimum Perl version to 5.6

      * IO::Compress::Zip
        - In one-shot zip, set the Text Flag if "-T" thinks the file is a
          text file.
        - In one-shot mode, wrote mod time & access time in wrong order
          in the "UT" extended field.
[perl #109264] ->method(my(...)) forcing lvalue cx

A simple my($foo,$bar) list is flagged as an lvalue:

$ ./perl -Ilib -MO=Concise -e 'my($foo,$bar)'
7  <@> leave[1 ref] vKP/REFC ->(end)
1     <0> enter ->2
2     <;> nextstate(main 1 -e:1) v:{ ->3
6     <@> list vKPM/128 ->7
3        <0> pushmark vM/128 ->4
4        <0> padsv[$foo:1,2] vM/LVINTRO ->5
5        <0> padsv[$bar:1,2] vM/LVINTRO ->6
-e syntax OK

That 128 that the list op is the same flag as LVINTRO.

When a method call is compiled, the list op for the argument list is
itself converted into an entersub op.  That LVINTRO flag is never
turned off.  So foo->bar(my($foo,$bar)) becomes this:

$ ./perl -Ilib -MO=Concise -e 'foo->bar(my($foo,$bar))'
9  <@> leave[1 ref] vKP/REFC ->(end)
1     <0> enter ->2
2     <;> nextstate(main 1 -e:1) v:{ ->3
8     <1> entersub[t4] vKMS/LVINTRO,TARG ->9
3        <0> pushmark sM/128 ->4
4        <$> const[PV "foo"] sM/BARE ->5
5        <0> padsv[$foo:1,2] lM/LVINTRO ->6
6        <0> padsv[$bar:1,2] lM/LVINTRO ->7
7        <$> method_named[PV "bar"] ->8
-e syntax OK

This was rarely a problem until commit da1dff948 added lvalue check-
ing for method calls (a fifth bug fix in that commit not mentioned in
the commit message).

Calling the method will now result in ‘Can't modify non-lvalue subrou-
tine call’ unless the method has the :lvalue attribute.

Before that, this would only cause problems with lvalue methods:

$ perl -le '
    sub clear_queue:lvalue { warn "called"; undef }
    3==main->clear_queue(my ($id, $name))
'
called at -e line 2.
Can't return undef from lvalue subroutine at -e line 3.

Calling it with ($id, $name) was fine, and allowed undef to
be returned.

Perl_localize in op.c (which is called for my, our and local)
calls my() (aka Perl_my_attrs) on the list itself for my or our.
Perl_my_attrs was setting flags on the list, not just on its children.

So this commit modifies my_attrs not to set any flags on the list
op itself.

local() was not affected, as it goes through op_lvalue_flags instead
of my_attrs, and op_lvalue_flags doesn’t set flags on list ops (I
mean ops of type OP_LIST, not listops in general).  I added tests for
it anyway.
feature.h: Mask hints in CURRENT_FEATURE_BUNDLE

Otherwise CURRENT_FEATURE_BUNDLE will end up including any hints added
later that happen to use higher bits.

This was causing autobox to turn off all features, causing failures
for Dist::Zilla::PluginBundle::AVAR.

I’m not adding tests for this, as such tests would need constant
tweaking in future perl developement.  What autobox is doing is
naughty and unsupported anyway.
Add Windows 2008 to the list of Windows versions in perlport
utf8.h: Restore macro defn incorrectly trashed earlier

Commit 66cbab2c91fca8c9abc65a7231a053898208efe3 changed the definition
of IN_UNI_8_BIT, but in so doing, lost the 2nd line of the macro; and I
did not catch it.  Tests will be added shortly.
Add the fc keyword in regen/feature.pl

It doesn't do anything yet.