From @Grinnz

Currently, the perlfunc entries for my, local, and state point to
documentation in perlsub which appears to be the in-depth documentation for
these keywords. Notably, our is instead detailed directly in its perlfunc
entry. I don't think it makes much sense to document these keywords in
perlfunc, since their use is largely unrelated to subroutines in any
meaningful way. Some other options may be documenting them in their
perlfunc entries more fully like our, or documenting them all (including
our as well) somewhere else like perlsyn or perldata. I would be happy to
work on a patch if there is any consensus on direction.

-Dan

(Perl)

From @Grinnz

On Tue, 10 Sep 2019 13​:11​:15 -0700, grinnz@​gmail.com wrote​:

I don't think it makes much sense to document these keywords in
perlfunc,

This of course should have said "in perlsub".

-Dan

From @jkeenan

On Tue, 10 Sep 2019 20​:11​:15 GMT, grinnz@​gmail.com wrote​:

Currently, the perlfunc entries for my, local, and state point to
documentation in perlsub which appears to be the in-depth documentation for
these keywords. Notably, our is instead detailed directly in its perlfunc
entry. I don't think it makes much sense to document these keywords in
perlfunc, since their use is largely unrelated to subroutines in any
meaningful way. Some other options may be documenting them in their
perlfunc entries more fully like our, or documenting them all (including
our as well) somewhere else like perlsyn or perldata. I would be happy to
work on a patch if there is any consensus on direction.

-Dan

(Perl)

FWIW, the commit which brought this documentation into pod/perlsub.pod was the 44th to commit to Perl 5, back in 1995. So we've lived with this positioning of the documentation for a long time.

Thank you very much.

--
James E Keenan (jkeenan@​cpan.org)

The RT System itself - Status changed from 'new' to 'open'