| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
And added a line to the module upgrades section.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Changed Module::Corelist and perldelta.pod
|
| |
|
|
|
|
| |
Updated Module::CoreList and perldelta to reflect the changes.
|
|
|
|
|
|
|
| |
- Manually added feature.
- Data::Dumper was upgraded while working on this; so we'll have to
redo the corelist, and adjust the "Updated Modules and Pragmata"
section.
|
|
|
|
|
|
| |
These functions can read beyond the end of their input strings if
presented with malformed UTF-8 input. Perl core code has been converted
to use other functions instead of these.
|
|
|
|
|
| |
These functions should be used in preference to the old ones which can
read beyond the end of the input string.
|
|
|
|
|
|
|
|
| |
The existing functions (utf8_to_uvchr and utf8_to_uvuni) have a
deficiency in that they could read beyond the end of the input string if
given malformed input. This commit creates two new functions which
behave as the old ones did, but have an extra parameter each, which
gives the upper limit to the string, so no read beyond it is done.
|
|
|
|
|
| |
These functions were replaced long ago, apparently in 5.8, but I didn't
verify that for sure.
|
| |
|
| |
|
|
|
|
| |
Also, fix the spelling of html.
|
|
|
|
|
| |
This won't change the rendered pod, but will clarify to anyone thinking to
patch the "mistake" that the seeming typo is intentional.
|
|
|
|
|
|
|
| |
Porting/bisect.pl is intended to cover 90% of use cases, whilst being simpler
to use than git bisect, so mention it first. Condense the description of
git bisect slightly - it's giving implementation details which duplicate
git help bisect, which we already refer the reader to.
|
|
|
|
|
| |
This both avoids cluttering the flow of manpage with auxiliary data, and
saves the user from having to extract the script from within the pod file.
|
|
|
|
| |
(Done as a second commit to avoid confusing git's rename detection.)
|
|
|
|
|
|
| |
Installing the Perl 5 to-do list as a manpage isn't that useful to anyone, as
it's a snapshot that becomes increasingly out of date. Much better to point
anyone interested in contributing direct to git HEAD, to view the current list.
|
| |
|
| |
|
|
|
|
| |
The behaviour was changed with commit 39ec54a59ce332fc.
|
|
|
|
| |
Documents the differences between 5.15.8 and 5.15.9.
|
|
|
|
|
|
| |
This reverts commit 21ffc8459b739cc13a32f22a2edb7be485a062e0.
Until I can figure out how to add a new perldelta and make all tests pass.
|
|
|
|
|
|
|
|
| |
pod/perl5159delta.pod"
This reverts commit 98f0737d71a92167bf1aace8a8d8411b985e3200.
Until I can figure out how to add a new perldelta and make all tests pass.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
dump, eval, evalbytes and wantarray are now only in "flow control".
local, my, our and state are only in "scoping".
prototype is now only in "misc". Whilst *prototypes* affect parsing, and
hence indirectly flow control, the prototype function is for introspecting
prototypes.
|
|
|
|
|
|
|
|
|
|
|
| |
Move the 3 non-function keywords into the summary cross reference section
at the end of perlfunc. Eliminate the examples which duplicate examples in
perlsyn. Merge the remaining 2 keywords into the "control flow" group.
Note that the switch feature is considered experimental.
With these changes, `perldoc -f default`, `perldoc -f given` and
`perldoc -f when` will still return a helpful result, and as before will
refer the reader to perlsyn for full information.
|
|
|
|
|
|
|
| |
perlfunc now has a section cross referencing keywords documented elsewhere.
Keywords are grouped by man page, and for most manpages, all the
cross-referenced keywords are in the same section. Hence make the L<> links
more specific by including the section.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also, make all indented code start with a four-space indent. Before
this it was inconsistent throughout.
|
| |
|
|
|
|
|
|
|
|
| |
Don’t refer people to warnings.pm for more information, as it
contains no more information about this variable.
Explain the scoping and also mention that the values are
considered internal.
|
| |
|
| |
|
|
|
|
|
|
| |
This was presumably brought in when I foolishly copied and pasted
the output from a version of groff that was over-eager to promote
"ugly" ASCII characters to "beautiful" non-ASCII ones.
|
|
|
|
|
|
|
| |
This should self-consistently and correctly identify when exec
will warn.
[ commit message rewritten by rjbs ]
|