| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Prior to the preceding commit, the ‘glob failed’ warning would always
occur, regardless of warnings settings, so W was never correct. Now
it is S, which is was it used to be closest to.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
It was already documented that when scanning for the end of the string,
backslashes escaping the closing delimiter are being eliminated; but
this is true for backslashes escaping backslashes as well. This makes
that C<< '.\.' eq '.\\.' >>. (Pointed out by Mithaldu)
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the record read feature was introduced in 5b2b9c687790241e8
in 1998 (but by Dan Sugalski, not Hans Mulder as the git history
erroneously says), sysread() was a couple of years from learning
about utf-8 and PerlIO was just a fancy way of calling stdio. The
documentation was reasonable given that environment.
Now it's potentially misleading to say that record reads are "the
equivalent of C<sysread>" because sysread on filehandles opened
with ":utf8" does characters, not bytes. The salient point about
the analogy with sysread was always that the read is unbuffered.
In the old days, this was in contrast to the buffering done in
stdio's fread(), but now it's in contrast to the buffering in the
perlio layer. By emphasizing the role of buffering, we can
actually shorten and simplify the docs.
Side note: Both Camel 3 and Camel 4 have the following problematic
statement in the documentation of $/: "Record mode mixes with line
mode only on systems where standard I/O supplies a read(3) function;
VMS is a notable exception." VMS certainly does have a read(3)
function and in fact that's what's used directly for record reads
(via PerlLIO_read) on VMS only. And as far as I know, it is
fread(), not read(), that is considered "standard I/O" everywhere.
N.B. Record reads on non-record-oriented files on VMS will likely
start using the same buffering as other platforms in a future
version of Perl.
|
|
|
|
|
|
| |
It's kind of late in the release process to change how $/ = \N works
for unicode streams, briefly document how broken it is and let the
user know it may change.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|