| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
explained in perldata.pod (see http://stackoverflow.com/questions/2997042/ )."
This reverts commit db2ed3fb308b082577e9315ba52b2cb266a2bd0a.
|
|
|
|
|
|
|
|
| |
perldata.pod (see http://stackoverflow.com/questions/2997042/ ).
A possible solution is to place an entry in perlvar.pod pointing out
that $# was removed and pointing the user to perldata.pod for the
explanation of $#ary usage.
|
| |
|
|
|
|
|
|
| |
I was looking for some actual values of $^O the other day and started
ack-ing t/. Turns out that this was documented in perlport. Link to
the relevant section to make it easy to find.
|
|
|
|
|
|
| |
See email thread for reference:
http://www.nntp.perl.org/group/perl.perl5.porters/2010/06/msg160812.html
|
| |
|
| |
|
|
|
|
| |
Change some lines so won't overflow 80 column width; make a link.
|
|
|
|
| |
(Spotted by Giel Goudsmit)
|
| |
|
| |
|
|
|
|
|
|
| |
This is achieved by introducing a new find_rundefsv() function in pad.c
This fixes [perl #75436].
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A number of function names that do warnings have been added, but diag.t
hasn't kept up.
This patch changes it to look for likely function names in embed.fnc, so
it will automatically keep up in the future. There's no need to worry
about it looking for inappropriate functions, as the syntax of messages
that it looks for is so restrictive, that there won't be false
positives. Instead there are still many messages it fails to catch.
As a result of it's falling behind several issues have crept in. I
resolved the couple I thought were clear (including one in a comment;
diag.t doesn't strip comments, but mostly it doesn't matter), and added
the others to the <DATA> section to ignore.
are
|
|
|
|
|
|
|
|
| |
Change to start with "C<die> raises an exception." and phrase in terms of
handling exceptions, and then how uncaught exceptions result in process exit.
Do not give details of the exit code in the first paragraph. Move this to a
later paragraph, clarify that $! is often unpredictable, and stress that 255
is the last resort exit code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Attached is a patch for some of this issue. I took Nicholas' advice,
and if the result of \cX isn't a word character, the output message will
precede it with a backslash, so the message in the example would be
"\c`" more clearly written simply as "\ " at -e line 1.
I think that message is true.
I also added tests.
There is a test that guarantees that we won't ship 5.14 with things as
they are now in it. I added wording to the comments next to that test
to be sure to verify with this email thread if we should remove the
deprecation, and mentioned that in the explanatory wording in the pod.
I support removing the deprecation, but for now I'm not touching that,
to see what other issues may yet arise before 5.14.
|
|
|
|
| |
And add a .t file to verify that it works.
|
|
|
|
|
| |
Prior to this patch, messages in perldiag.pod had to have \\ instead of
the correct single backslash in order for diag.t to not complain.
|
| |
|
|
|
|
| |
This is suitable for 5.12.2, but not many people use this feature.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
perlebcdic.pod contains a helpful table to use in tr/// to convert
between EBCDIC and Latin1/ASCII. Unfortunately, the table is the
inverse of the one it describes, as I discovered in following the
directions on how it was extracted.
The actual code that uses the table uses it in the inverse way, so it
actually works correctly, but if you follow the instructions to get the
tables corresponding to the other recognized code pages, you will get
the inverse of the ones you wanted, and things won't work out.
This patch changes the table to its inverse, and changes the sample code
to correspond, as this is easier for the person trying to follow the
instructions since deriving the old table is somewhat more complicated.
I also changed the table to hex from octal, as that is more the norm
these days, and I changed to recipes in the pod to print out leading
zeros to make all the values the same length, as the table that they can
generate has them.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes s/// so that it doesn't act destructively on its target.
Instead it returns the result of the substitution (or the original string if
there was no match).
In addition this patch:
* Adds a new warning when s///r happens in void context.
* Adds a error when you try to use s///r with !~
* Makes it so constant strings can be bound to s///r with =~
* Adds documentation.
* Adds some tests.
* Updates various debug code so it knows about the /r flag.
* Adds some new 'r' words to B::Deparse.
|
|
|
|
|
|
| |
Package block syntax limits the scope of the package declaration to the
attached block. It's cleaner than requiring the declaration to come
inside the block.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
And tweak its documentation.
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The function perl_ebcdic_control() is unnecessary, as the toCTRL macro
that calls it can be changed to just map EBCDIC to ASCII first, and then
doing the normal procedure.
This means that EBCDIC and ASCII will no longer diverge. Currently,
EBCIDIC gives a syntax error for inputs outside its domain, whereas the
ASCII version accepts some of them.
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* 'blead' of ssh://perl5.git.perl.org/gitroot/perl:
Return 0 (with a warning) for sprintf("%.0g") and sprintf("%.0f")
Updating list of DOSish perls in perlport.pod.
Add Porting/checkpodencoding.pl to MANIFEST
separate the 0755 from the . $TAINT0. this silences the warning "Dot after octal literal is concatenation".
Clarify that mail to perlbug also goes to p5p
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The wording added in 64a8e22bd3 didn't clarify that mail to perlbug is
also forwarded to perl5-porters. Make this section clearer so that it
now explains that perlbug is just perl5-porters + RT tracking.
See the discussion after Craig A. Berry's comment in RT #73914 for
reference.
|
|/ / |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|