| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In L<perlunicode/"User-Defined Character Properties">, it says you can
create custom properties by defining subroutines whose names begin with
"In" or "Is". However, perl doesn't actually enforce that naming
restriction, so \p{foo::bar} will call foo::Bar() if it exists.
This commit finally enforces this convention. Note that this broke a
number of existing tests for properties, since they didn't always use an
Is/In prefix.
(cherry picked from commit d658a8a81c4f311bef688fd51df924a424429f14)
|
|
|
|
|
|
| |
based on CGI 3.50, patches supplied by Nino Tyni of Debian
http://markmail.org/message/f3onn6dkkcswlsui
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
gv_init() has name and len args, but newCONSTSUB() (which it calls)
doesn't have a len arg, so any trailing garbage in name gets used by
newCONSTSUB.
In the test case, this means that we end up attaching the const CV
to both the "FOO" and qq{FOO, "\\n";\n} GVs. So it gets freed twice.
|
|
|
|
| |
Use an intermediate variable cv to avoid lots of GvCV(gv)'s
|
| |
|
| |
|
|
|
|
| |
(could not be simply cherry-picked)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As outlined in the RT ticket due to miniperl's dependencies differing to
the final perl binary dtrace -G needs to be called separately for each.
Build tested on Mac OS X 10.6, Solaris 11 and Scientific Linux with
SystemTap from git.
(Solaris is the only system I have access to where DTRACE_O actually gets
defined. Neither the dtrace binary on OS X nor SystemTap's dtrace
compatibility layer accept the -G option.)
(cherry picked from commit 3d450a5dd4e8f9a7b2aba0b018f9fe078fb6aa30)
|
|
|
|
| |
(cherry picked from commit d9bf0e0a91525fcdd8099d78b891aa20066e9d1c)
|
| |
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
| |
|
|
|
|
|
|
| |
I don't know where the text for the stuff below this new heading should
go, but it clearly doesn't belon with what came before, so add a heading
to separate them, perhaps rearranging things later
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Change some lines so won't overflow 80 column width; make a link.
|
|
|
|
|
|
| |
The \p{Posix...} classes had not gotten added yet to the ref pod; there
were some reformattings to make things display properly in an 80 column
window.
|
|
|
|
|
| |
While not strictly wrong, the hre was missing info for what \p{Punct}
does.
|
|
|
|
|
|
|
|
|
|
|
| |
This addresses runtime errors in Module::Build::Platform::cygwin
as reported by Jesse Vincent. The changes are backported from
the Module::Build repository and the version number has been
slightly incremented to indicate a change from the version on CPAN.
This hopefully addresses test errors in t/actions/installdeps.t, but
the error seems specific to building perl on cygwin and has not been
reported when Module::Build was tested on cygwin by CPAN Testers.
|
|
|
|
|
|
| |
The controls all now have names, and the part about \c\ has been
corrected. The table widths have been changed; all recipes have been
tested on the new tables.
|
|
|
|
|
|
| |
A number of clarification and wording edits have been made, fixing some
broken links, and details especially on \d in the Unicode range. Fixed
an incorrect character ordinal
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Make accurate the advice about eighth-bit set characters, and a few
editing improvements.
|
| |
|
|
|
|
|
|
|
| |
"GETTING ACCESS TO THE REPOSITORY" is a bit too loud compared to
"Getting access to the repository". The POD standard itself doesn't
have anything to say about this, but most of our long =head1 sections
in pod/*.pod don't use all-caps.
|
|
|
|
|
|
|
| |
The first sentence is stolen from Git's own
Documentation/SubmittingPatches. We have a lot of commit messages that
overflow `git log --pretty=oneline', but it wouldn't hurt if we change
that sooner rather than later.
|
|
|
|
| |
Signed-off-by: David Golden <dagolden@cpan.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The attached patch teaches pp_leavesublv about kine.
For the record, a binary search points its digit at:
From: Nicholas Clark <nick@ccl4.org>
Date: Mon, 6 Jun 2005 09:08:45 +0000 (+0000)
Subject: Shared hash key scalars can be safely copied as shared hash key scalars
Shared hash key scalars can be safely copied as shared hash key scalars all the time.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
I noticed two dubious expressions that look as if they were
intended to be assignments. The comment above the code says
it's broken.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When perlio flushes down to the unix layer, it can introduce a
spurious record boundary when writing to a record-oriented file.
Perl may create such files when doing edit-in-place or any other
context where the file format is inherited from a previous
version of the file.
The problem can be eliminated by enabling line buffering on such
files when they are opened. This was a regression in 5.10.0 since
before that stdio's buffering performed the same function.
N.B. Lines longer than the size of the perlio buffer will still
result in multiple records -- a larger buffer may be necessary.
For more details and discussion see:
http://www.nntp.perl.org/group/perl.vmsperl/2010/11/msg15419.html
Thanks to Martin Zinser for the problem report.
|