Skip to content

Commit a53664e

Browse files
committed
perlapi: How to find when API item added to Perl
This adds text to this pod that shows how to use ppport to find when an API element came into being in perl
1 parent 6a491f8 commit a53664e

File tree

2 files changed

+16
-1
lines changed

2 files changed

+16
-1
lines changed

autodoc.pl

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2781,6 +2781,20 @@ ($destpod)
27812781
|to be documented. Patches welcome! The interfaces of these are subject to
27822782
|change without notice.
27832783
|
2784+
|To find out what release an element came into being, use
2785+
|
2786+
| perl dist/ppport.h --api-info=element
2787+
|
2788+
|You may also use a pattern
2789+
|
2790+
| perl dist/ppport.h --api-info=/./
2791+
|
2792+
|displays all possible public api elements, but not items in L<perlintern>.
2793+
|Some elements have been backported in L<Devel::PPPort> so that they are
2794+
|usable in earlier versions than they otherwise would be available. The
2795+
|display also includes information as to what the earliest possible version
2796+
|such an element may be used in; as well as some hints and cautions.
2797+
|
27842798
|Some of the functions documented here are consolidated so that a single entry
27852799
|serves for multiple functions which all do basically the same thing, but have
27862800
|some slight differences. For example, one form might process magic, while

pod/perldelta.pod

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,8 @@ Additionally, the following selected changes have been made:
184184

185185
=item *
186186

187-
XXX Description of the change here
187+
L<perlapi> now contains information about how to find what release of
188+
Perl first contained an API element
188189

189190
=back
190191

0 commit comments

Comments
 (0)