Remove EFS escapes in unixify without directory components.

When converting a VMS file specification containing caret escapes
for extended characters to Unix format, we need to remove those
escapes.  We were doing so for paths containing directory
components but we also need to do it for bare filenames.  I.e.,
this was working:

disk:[dir]foo^%bar --> /disk/dir/foo%bar

but this was not (until now):

foo^%bar --> foo%bar
Add use_versioned_archname to Configure

This patch adds 'use_versioned_archname' as a Configure option.
When set, it includes 'api_versionstring' in 'archname'. E.g.
x86_64-linux-5.13.6-thread-multi.  It is unset by default.

This feature was requested by Tim Bunce, who observed that
INSTALL_BASE creates a library structure that does not
differentiate by perl version.  Instead, it places architecture
specific files in "$install_base/lib/perl5/$archname".  This makes
it difficult to use a common INSTALL_BASE library path with
multiple versions of perl.

By setting -Duse_versioned_archname, the $archname will be
distinct for architecture *and* API version, allowing mixed use of
INSTALL_BASE.

This patch demonstrates the desired effect for discussion.  Actual
changes would need to be made upstream in metaconfig and
integrated back into blead.
makemeta no longer relies on the currently executing perl for version
Make makemeta more cognisant and easier to use

Provide -y and -j switches to produce yml or json
files, respectively, for use in regen rules and tests

The default behaviour is to produce both files.

Update release managers' guide to say to regen the
META files before generating release tarballs.
Update Pod-Parser to CPAN version 1.60

  [DELTA]

  [Pod-Parser]

  31-Jan-2013           Marek Rouchal                        <marekr@cpan.org>
  -----------------------------------------------------------------------------
  Version 1.60
  + removed Pod::Checker and Pod::Usage from this distribution - they are now
    separate distros and are subjects to be refactored, to be based upon
    Pod::Simple. Thanks to rjbs for reminding me of this.

Add Pod-Checker and Pod-Usage to cpan/

These have been split out of Pod-Parser

  [Pod-Checker]

  27-Jan-2013           Marek Rouchal                        <marekr@cpan.org>
  -----------------------------------------------------------------------------
  Version 1.60
  + preparation of changing this module to use Pod::Simple
    refactored the Pod-Parser distribution and moved all things Pod::Checker
    to this new distribution package
  + CPAN RT#79535: Pod::Checker synopsis for podchecker is opposite
    corrected the POD synopsis
  + factored this distribution out of Pod-Parser-1.51

  [Pod-Usage]

  1.61 (marekr)
  - fix empty META.yml (CPAN RT#83118: META.yml is empty)
  - update outdated test expected data (CPAN RT#83111: fails test)
 
  1.60 (marekr)
  - moved POD behind __END__ for slighlty quicker loading
  - CPAN RT#81387: 2 suggestions for module Pod::Usage
    added example of how to use FindBin to locate the script;
    added $Pod::Usage::Formatter to allow a different base class
  - CPAN RT#75598: [PATCH] Don't use perldoc if it is missing
    implemented as suggested in the RT ticket
  - factored Pod::Usageout of the Pod-Parser distribution into a separate one,
    in order to prepare the rewrite based upon Pod::Simple
  - thanks to rjbs for driving this
Make vmsify support files with no directory component.

We've been assuming there is always a directory portion to a path
being converted to VMS format, and it's true that translating
directory delimiters and such is the most noticeable aspect of
such conversions.  But we also depend on the conversion to add
caret escapes to characters in the path that are only valid when
using Extended Filename Syntax (EFS), but weren't doing that
for paths with no directory component.

I.e., this was working:

/disk/dir/foo%bar --> disk:[dir]foo^%bar

but this was not (until now):

foo%bar --> foo^%bar

Since we're now working on a pointer that has not necessarily
been incremented while adding directory syntax, we also add
a number of guards to make sure we don't peek beyond the
beginning of the result string.

N.B.  There will be a separate commit following shortly that
prevents paths with no directory component from being passed
through as-is -- here we just provide the infrastructure to
make that possible.
Pass-through handling (again) in tovmsspec.

This is a partial retreat from b3efb2487fa7, where we started
passing through all ambiguous filespecs without modification. We
can now process the majority of cases that aren't macros, following
59247333b91 and various other commits that improved the escaping
of dots.  So for now we'll attempt to process these and pass
through macros only.
Remove unused feature setting from vms/vms.c.

This feature was apparently intended to enable workarounds for
handling filespec translations on paths with no directory component.
Many (most?) of the problems with such paths have now been fixed,
and the feature itself was never actually used, so we're better
off without it.
Benchmark iteration warnings should warn, not print
reword release announcement template
add example of warning categorization to perldiag
Update File-CheckTree to CPAN version 4.42

  [DELTA]

  4.42  Thu Feb  7 15:51:35 EST 2013
    * add warning (for core-installed copy only) indicating File::CheckTree
      will be removed from core in 5.20.0
Update Text-Soundex to CPAN version 3.04

  [DELTA]

  3.04  Thu Feb  7 15:53:09 EST 2013 <rjbs@cpan.org>

  The module is going to be removed from the core distribution of perl, and will
  now warn (under warnings) if loaded from its installed-to-core location.
Updated File::Temp from 0.22 to 0.22_90
embed.fnc: Remove inappropriate 'p' flags

These functions do not begin with 'Perl_'; currently this flag is
ignored here.
regen/embed.pl: Warn if have > 1 i, p, and s flags

These should be mutually exclusive
regen/embed.pl: Extract out duplicate code into a fcn
makedef.pl: Don't export inline fcns

An inline function is static to the file it is defined in.  But they can
be part of the public API if they are in #included header files and
defined in embed.fnc.  Normally such functions are written to the export
list on platforms that have this, but since they are static, you get a
linkage error.  This commit suppresses the writing of inline functions
Change name 'av_top' to 'av_top_index'

 In using the av_top() function created in a recent commit, I found
 myself being confused, and thinking it meant the top element of the
 array, whereas it really means the index of the top element of that
 array.  Since the new name has not appeared in a stable release, it can
 be changed, without remorse, to include 'index' in it.
Inline av_top_index()

This function is just an assert and a macro call.  Avoid the function
call overhead by making it inline.