/*
=for apidoc m|PADOFFSET|pad_alloc_name|SV *namesv|U32 flags|HV *typestash|HV *ourstash
-Allocates a place in the currently-compiling pad (via L</pad_alloc>) and
+Allocates a place in the currently-compiling
+pad (via L<perlapi/pad_alloc>) and
then stores a name for that entry. I<namesv> is adopted and becomes the
name entry; it must already contain the name string and be sufficiently
upgraded. I<typestash> and I<ourstash> and the C<padadd_STATE> flag get
-added to I<namesv>. None of the other processing of L</pad_add_name_pvn>
+added to I<namesv>. None of the other
+processing of L<perlapi/pad_add_name_pvn>
is done. Returns the offset of the allocated pad slot.
=cut
pod/perl.pod Verbatim line length including indents exceeds 80 by 9
pod/perlaix.pod Verbatim line length including indents exceeds 80 by 11
pod/perlapi.pod ? Should you be using L<...> instead of 86
-pod/perlapi.pod Verbatim line length including indents exceeds 80 by 144
+pod/perlapi.pod Verbatim line length including indents exceeds 80 by 154
pod/perlapi.pod unresolved internal link 3
pod/perlapio.pod Verbatim line length including indents exceeds 80 by 5
pod/perlbeos.pod ? Should you be using F<...> or maybe L<...> instead of 5
pod/perlhpux.pod Verbatim line length including indents exceeds 80 by 2
pod/perlhurd.pod Verbatim line length including indents exceeds 80 by 2
pod/perlintern.pod ? Should you be using L<...> instead of 5
-pod/perlintern.pod Verbatim line length including indents exceeds 80 by 26
+pod/perlintern.pod Verbatim line length including indents exceeds 80 by 22
pod/perlinterp.pod ? Should you be using L<...> instead of 1
pod/perlinterp.pod Verbatim line length including indents exceeds 80 by 1
pod/perlintro.pod Verbatim line length including indents exceeds 80 by 11