It is and always will be safe to delete the most recent key returned from each.
Don't rely on IPC::Cmd in ExtUtils-Install tests
Handle "no versions" feature in fileify and tovmsspec.

This is a follow-up to d5e61aaf9d7051b136, where we stopped
escaping semicolons in tovmsspec when they appeared to be the
beginning of a version specification but always escaped them
otherwise.

It turns out there is yet another CRTL feature logical name
(DECC$FILENAME_UNIX_NO_VERSION) that tells us a Unix-format
specification is not allowed to have a version number, so in
that case, always escape the semicolon since it can't be the
start of a version specification.

Also, don't add the version number when fileifying directory
specs if this "no versions" feature is in effect.
don't repeatedly call HvUSEDKEYS

HvUSEDKEYS contains a function call nowadays. Don't call it repeatedly.
remove a redundant SvTIED_mg from S_do_smartmatch

A non tied HV potentially could be checked twice for being tied. Move
HvUSEDKEYS part to avoid checking var tied twice. The redundant tied check
comes from day 1 of smart match in commit 0d863452f5 . IDK why HV sides
are swapped, but comment it.
ExtUtils-Install-1.62 has been released to CPAN
perldiag: Clarify that lexicals do not trigger "used only once"
perlfunc: layout getpw*&c return values as a table
Backport/genererate work from cross-port

At the "Perl5 and beyond" hackathon early feb 2014 in Amsterdam, hugmeir
and I walked through all the changes and ended up with a serious warning
in metalint where we stopped. The warning proved to be a bug in metalint
that will be fixed in the future and has a rather easy workaround.

Porting/Glossary is not yet being generated correctly. Will take care of
that later.
Make the ExtUtils-Install tests parallelisable
Update ExtUtils-Install Changes file
regen/regcharclass.pl: Generate correct macro instead of skipping

It makes no sense to check for length safeness for The macros generated
by this program which take a single UV code point as a parameter. Prior
to this patch, it would skip trying to generate them if asked.  But,
because of the way things are structured, that means that if you need
just this and the safe versions, you can't do it so easily.  What this
commit does is generate the cp macro if requested even if the 'safe'
version of other macros are also requested.
regen/regcharclass.pl: Don't generate unused macros

Having these unused macros around just clutters up the header file
regcomp.c: Make SSC node clone safe

This just sets the ptr field in the Synthetic Start Class that will be
passed to regexec.c NULL, and clarifies the comments in regcomp.h.  See
the thread starting at http://markmail.org/message/2txwaqnjco6zodeo
sprinkle LIKELY() on pp_hot.c scope.c and some *.h

I've gone through pp_hot.c and scope.c and added LIKELY() or UNLIKELY()
to all conditionals where I understand the code well enough to know that
a particular branch is or isn't likely to be taken very often.

I also processed some of the .h files which contain commonly used macros.
regcomp.c: Don't read past string-end

In doing an audit of regcomp.c, and experimenting using
Encode::_utf8_on(), I found this one instance of a regen/regcharclass.pl
macro that could read beyond the end of the string if given malformed
UTF-8.  Hence we convert to use the 'safe' form.  There are no other
uses of the non-safe version, so don't need to generate them.
Upgrade to Thread::Queue 3.04
Update ExtUtils-MakeMaker to CPAN version 6.92

  [DELTA]

6.92 Thu Mar 13 16:18:32 GMT 2014

    No changes from 6.91_01

6.91_01 Thu Mar  6 13:48:22 GMT 2014
    Test fixes:
    * Make meta tests more robust to changes in CPAN::Meta
lib/locale.t: Fix broken test

The test that [:digit:] is a subset of [:xdigit:] failed in locales
where  [:digit:] matches 2 blocks of 10 digits, but the second block
isn't considered part of [:xdigit:].  This happens in Thai on Windows.
The POSIX standard http://pubs.opengroup.org/onlinepubs/9699919799/
does not use very clear language, but I'm taking it as meaning it is ok
for this to happen, so this revises the test to accept it.
PATCH: [perl #121340] lib/locale.t noisy+complaining but passes on Win32

It turns out that these messages were not printed as one would expect
under TAP, but were output using warn().