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