PATCH: [perl #122084] BBC KARMAN/Search-Tools

The problem was that a function was defined only in PERL_CORE, and
embed.fnc just needed to change to grant access outside that.
t/re/pat_advanced.t: Add comment
PATCH: [perl #122029] BBC KAWASAKI/Encode-JP-Emoji

This turns out to be that the code was only getting the compile-time
package name, and it needs to be expanded to get the correct run-time
name.
regcomp.c: White-space only

Indent because of newly-formed block
op.c: Fix typo in comment
Fatalize using hash|array as reference

This has been deprecated, scheduled to come out in 5.22
For HP-UX, do not potentially deref NULL CopFILESV.

(HP-UX and other ARG_ZERO_IS_SCRIPT platforms)
Do not printf U32 and I32 (both) as %i.

(Detected in HP-UX.)
d_namlen can be signed.

In HP-UX, it is either short or char (which can be either signed or unsigned),
depending on the compiler flags.
Use of the Uid_t_sign and casting instead of Uid_t_f.

HP-UX B.11.31/64 gcc 4.7.2 with -DDEBUGGING:
taint.c:38:2: warning: format '%ld' expects argument of type 'long int', but argument 5 has type 'uid_t' [-Wformat]

This removes the sole use of Uid_t_f (and there are none of Gid_t_f)
from the core.
Disable and document xop_name gcc warning seen in HP-UX.
be explicit that SvSetSV() doesn't do set magic
Fatalize defined(@) and defined{%)

Calling defined on an array or hash has been deprecated and scheduled
for removal in v5.22.  This commit does that, removing the tests that
assumed they were defined.

In order to get the line numbers of the errors to display, I combined
the first and second lines of the message, omitting the \n
Use Unicode 7.0
perldiag: Remove obsolete entries.

These entries about \b{} are obsolete, as it no longer is deprecated,
but forbidden.
perldiag: Add details about variable length lookbehind

See http://nntp.perl.org/group/perl.perl5.porters/215685
Remove support for ?PATTERN? without explicit 'm' operator

This has issued a deprecation warning since v5.14 (commit 725a61d70),
and precludes using ? as an operator after a unary operator that
defaults to $_, such as:

   ref ? $_ : [$_]
Remove "ternary operator parsed as search pattern" warning

Since ?PATTERN? without 'm' is no longer supported, there is no
ambiguity any more.
Preserve explicit 'm' when deparsing m?PATTERN?

Bare ?PATTERN? is no longer allowed
Bump B::Deparse version