| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Add a new warning "Missing argument in %s"
|
| | |
|
| | |
|
| |
|
|
|
| |
Also add a test for that, fill in test description, and sneak in a vim
modeline for re_tests
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
| | |
|
| |
|
|
| |
The man standard requires the title to be on one line.
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
(It needs to be this way to make search.cpan.org generate the right links)
This step is already described in release_managers_guide.pod.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The docs to unlink didn't explicitly note that it set $! on
failure, unlike the docs on some other system calls do.
While I was in there, I cleansed the entry a little and
added an example of unlinking files one-by-one to find
the ones that fail.
Modern Perl fix: let's call a glob a glob() and not a <*>.
This problem was noted on the Perl Beginner's list:
http://www.nntp.perl.org/group/perl.beginners/2009/11/msg110062.html
|
| | |
|
| |
|
|
|
| |
This comes from 028b6d17a07335707c2b234cb69ac4051ed48435 in
git@github.com:briandfoy/perlfaq.git
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The example wanted to sort a list like qw(=1 =2 =a =3 =d). One
example tried to be clever with array indices and precomputed
an array in @nums. However, it forgot to leave holes for the
elements where it could not extract a run of digits. Once the
indices were misaligned, the sort didn't give the right answer.
I know you can read the patch, but since I fixed whitespace too,
a simple diff gives you a lot of output. The old example had:
for (@old) {
push @nums, /=(\d+)/;
push @caps, uc($_);
}
The new one keeps the indices aligned by using undef when the
match failed:
for (@old) {
push @nums, ( /=(\d+)/ ? $1 : undef );
push @caps, uc($_);
}
This issue was reported on Stackoverflow:
http://stackoverflow.com/questions/1754441
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Abigail <abigail@abigail.be>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The attached patch contains these fixes for the lexer API work:
* fix MinGW-revealed problem in BOM logic (replacing Jan's patch)
* fix warnings from t/op/incfilter.t
* probably fix g++ failure due to goto bypassing initialisation
* perl5112delta update
-zefram
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
{,users.}per5.git.perl.org
And run podtidy.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Attached is a patch that adds a public API for the lowest layers of
lexing. This is meant to provide a solid foundation for the parsing that
Devel::Declare and similar modules do, and it complements the pluggable
keyword mechanism. The API consists of some existing variables combined
with some new functions, all marked as experimental (which making them
public certainly is).
|
| |
|
|
|
|
|
|
|
| |
The message ‘localtime(...) too large’ is not documented in perldiag.
The attached patch adds it. I know it’s technically ‘%s(%.0f) too
large’, but it’s easier for users to find it under ‘localtime’ and
‘gmtime’. I also had to modify diagnostics.pm to support %.0f, and I
added a test, but I used a hack with STDERR that would make debugging
very difficult to anyone else adding tests.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Attached is a patch that changes how the tokeniser looks up subroutines,
when they're referenced by a bareword, for prototype and const-sub
purposes. Formerly, it has looked up bareword subs directly in the
package, which is contrary to the way the generated op tree looks up
the sub, via an rv2cv op. The patch makes the tokeniser generate the
rv2cv op earlier, and dig around in that.
The motivation for this is to allow modules to hook the rv2cv op
creation, to affect the name->subroutine lookup process. Currently,
such hooking affects op execution as intended, but everything goes wrong
with a bareword ref where the tokeniser looks at some unrelated CV,
or a blank space, in the package. With the patch in place, an rv2cv
hook correctly affects the tokeniser and therefore the prototype-based
aspects of parsing.
The patch also changes ck_subr (which applies the argument context and
checking parts of prototype behaviour) to handle subs referenced by an
RV const op inside the rv2cv, where formerly it would only handle a gv
op inside the rv2cv. This is to support the most likely kind of
modified rv2cv op.
The attached patch is the resulting revised version of the bareword
sub patch. It incorporates the original patch (allowing rv2cv op
hookers to control prototype processing), the GV-downgrading addition,
and a mention in perldelta.
|
| | |
|
