Father Chrysostomos [Sun, 27 May 2012 18:22:51 +0000 (11:22 -0700)]
perlfunc: two missing words
This odd sentence was introduced in
8f1da26d.
Tony Cook [Mon, 28 May 2012 13:59:20 +0000 (23:59 +1000)]
Tony Cook [Tue, 8 May 2012 06:42:19 +0000 (16:42 +1000)]
[perl #112272] return EEXIST on link() to an existing file
Also attempts to translate some other errors.
Unfortunately Microsoft don't document error codes.
Tony Cook [Mon, 7 May 2012 12:23:42 +0000 (22:23 +1000)]
[perl #112272] test link()'s error returns (TODO)
Yves Orton [Mon, 28 May 2012 08:58:06 +0000 (10:58 +0200)]
Revert "fix [perl #76546] regex engine slowdown bug"
This reverts commit
dee29c6b5bec1d6e7fccc971e31113a5d7cee844.
$ perl5.16.0 -e 'warn "t/bin/good.pl syntax OK\n" =~ /syntax OK\s+\z/si'
1 at -e line 1.
$ bleadperl -e 'warn "t/bin/good.pl syntax OK\n" =~ /syntax OK\s+\z/si'
Warning: something's wrong at -e line 1.
Will fix properly later.
Steve Hay [Mon, 28 May 2012 08:53:57 +0000 (09:53 +0100)]
Update checkAUTHORS.pl with missing author
N/K [Mon, 28 May 2012 08:33:58 +0000 (09:33 +0100)]
[perl #111798] ExtUtils-CBuilder looks for the manifest file in the wrong place
Near the start of link(), $output gets set to a blib\arch\auto path.
A little later that gets copied into $spec{output}, but $spec{manifest}
is left unset so it gets set later to a $spec{builddir} path, which is
not what $spec{output} was set to earlier.
The manifest file is always created alongside the DLL, so the correct
fix is simply to append '.manifest' to the DLL path to find the manifest.
(EU-MM does that too.)
Patch taken from [cpan #35943] which reported the same problem. The other
concern raised there, about the VC version being checked to deduce the
existence of the manifest file rather than testing that directly, has
long since been incorporated already and also explains why this problem
has not been seen recently: the faulty attempt to embed the manifest has
not been attempted ever since the existence test was added because it was
also failing and hence no 'mt' command was being run. [cpan #35943] is
thus resolved by this change too.
Bump $VERSION in all ExtUtils::CBuilder files (to 0.280208) to keep them
all in sync as before.
Steve Hay [Mon, 28 May 2012 07:35:19 +0000 (08:35 +0100)]
[perl #111782] ExtUtils-CBuilder on Windows does not embed manifests
Correct the test for the existence of the manifest file.
Bump $VERSION in all ExtUtils::CBuilder files (to 0.280207) to keep them
all in sync, as is currently the case.
Chris 'BinGOs' Williams [Sun, 27 May 2012 21:35:02 +0000 (22:35 +0100)]
Synchronise Module-CoreList in Maintainers.pl for v5.17.0 release
Ricardo Signes [Sun, 27 May 2012 13:32:27 +0000 (09:32 -0400)]
update release schedule; 5.17.3 is Steve Hay
Yves Orton [Sun, 22 Apr 2012 13:58:32 +0000 (15:58 +0200)]
fix [perl #76546] regex engine slowdown bug
Breno G. de Oliveira [Fri, 25 May 2012 13:44:47 +0000 (10:44 -0300)]
Add missing author for 5.11.2 epigraph
Brian Fraser [Sat, 26 May 2012 20:35:26 +0000 (17:35 -0300)]
Fix for [perl #9423] vec assignments generate 2 warnings
Before this commit, this:
vec(my $v,0,1) = 1;
would've produced four warnings about uninitialized values;
however, the ticket argued that these were spurious.
This commit removes the warning in the case of lvalue vec, since it is
similar to |=, but leaves it in place for rvalue vec.
Brian Fraser [Sat, 26 May 2012 01:30:02 +0000 (22:30 -0300)]
sv.c: Make sv_pvn_force_flags guard against SV_UNDEF_RETURNS_NULL.
Previously, if SV_UNDEF_RETURNS_NULL was passed to sv_pvn_force_flags,
it would call sv_2pv_flags with that flag, and get back a NULL instead
of a char *, which lead to issues.
This commit makes sv_pvn_force_flags use an empty string in that case.
Florian Ragwitz [Mon, 26 Mar 2012 12:51:50 +0000 (14:51 +0200)]
CPAN's Term::ReadLine has been synchronised
Father Chrysostomos [Sat, 26 May 2012 21:12:56 +0000 (14:12 -0700)]
File::Spec::Unix: Fix pod link
Father Chrysostomos [Sat, 26 May 2012 20:31:30 +0000 (13:31 -0700)]
Add Volker Schatz to AUTHORS
Father Chrysostomos [Sat, 26 May 2012 20:30:36 +0000 (13:30 -0700)]
Increase $File::Spec::Unix::VERSION to 3.39_03
Volker Schatz [Sat, 26 May 2012 20:29:54 +0000 (13:29 -0700)]
Tests for perl #111510
Volker Schatz [Sat, 26 May 2012 19:32:25 +0000 (12:32 -0700)]
[perl #111510] File::Spec::UNIX->abs2rel() gets it wrong with ".." components
File::Spec::UNIX->abs2rel() returns wrong results in a few cases, most
of which involve ".." path components.
To reproduce, paste the following test cases into:
perl -MFile::Spec::Unix -n -e 'print File::Spec::Unix->abs2rel(split),"\n";'
../foo bar/bat
bar/bat ../foo
foo bar/../bat
. .
/ /
Correct results when run at /home/me and no symlinks in base path:
../../../foo
../me/bar/bat
../foo
.
.
Results for File::Spec::Unix from PathTols 3.33:
../../foo
../bar/bat
../../../foo
/
/
The error in the first test case is due to an optimisation applied when
both arguments are relative paths, which prepends "/" instead of the
current directory. "/../" is then converted to "/" by canonpath().
I have replaced this optimisation by a single call to _cwd() in the
following patch. This also fixes the fourth test case. Besides, I have
moved checks which make sense only for absolute path arguments to the
first branch of the if.
(hunk @@ -366,28 +367,32 @@)
The error in the last test case arises because a root dir $base is
treated specially, and catdir() does not work well for fewer than two
path components. The first added line in the following patch catches that.
As regards the second and third test case, they can be solved without
consulting the filesystem only if no symlinks are involved. Whereever
$path contains .. components, the corresponding directory has to be
descended into. The following patch does this.
(hunk @@ -395,19 +400,39 @@)
It can be impossible for abs2rel() to work correctly without looking at
the filesystem if $base contains symlinks. I understand from the
documentation that the File::Spec modules are not meant to consult the
filesystem. Even though the docs state that abs2rel() does not consult
the filesystem, the implications could perhaps be made clearer, for
example like this:
(hunk @@ -352,9 +352,10 @@)
Aristotle Pagaltzis [Tue, 15 May 2012 16:59:33 +0000 (18:59 +0200)]
rewrite installhtml's installdir dir scan logic
The code so far was riddled with copy-paste and hacks and incurred
redundant effort, including syscalls. Replaced with a skimmable and
parsimonious implementation.
Aristotle Pagaltzis [Wed, 16 May 2012 02:47:29 +0000 (04:47 +0200)]
turn some quasi-declarations into real inline ones
Aristotle Pagaltzis [Tue, 15 May 2012 16:59:31 +0000 (18:59 +0200)]
switch installhtml from File::Spec to ::Functions
The plan in the next commits is to use C<no_upwards> from File:::Spec to
be explicit about intent -- imported using File::Spec::Function to avoid
the ugly File::Spec class method calling convention. This patch would be
frivolous otherwise, but given the occasion we might as well make things
consistent.
Ricardo Signes [Sat, 26 May 2012 17:44:26 +0000 (13:44 -0400)]
record some more release volunteers
Ricardo Signes [Sat, 26 May 2012 17:22:09 +0000 (13:22 -0400)]
note that there is another file to edit on perlweb
Zefram [Sat, 26 May 2012 16:57:51 +0000 (17:57 +0100)]
link to 5.17.0 release announcement
Zefram [Sat, 26 May 2012 16:38:31 +0000 (17:38 +0100)]
new perldelta
Zefram [Sat, 26 May 2012 16:19:36 +0000 (17:19 +0100)]
epigraph for 5.17.0
Zefram [Sat, 26 May 2012 14:06:57 +0000 (15:06 +0100)]
fix perlhist entry for 5.16.0
Zefram [Sat, 26 May 2012 14:05:01 +0000 (15:05 +0100)]
add new release to perlhist
Zefram [Sat, 26 May 2012 14:03:04 +0000 (15:03 +0100)]
update Module::CoreList for 5.17.0
Zefram [Sat, 26 May 2012 14:01:51 +0000 (15:01 +0100)]
note Module::CoreList issue with .0 versions
Zefram [Sat, 26 May 2012 13:55:38 +0000 (14:55 +0100)]
handle hash form of bugtracker resource data
The format changed with version 2 of the META spec.
Zefram [Sat, 26 May 2012 13:52:08 +0000 (14:52 +0100)]
handle JSON meta files on CPAN
Zefram [Sat, 26 May 2012 12:40:28 +0000 (13:40 +0100)]
finalise perldelta
Zefram [Sat, 26 May 2012 12:34:20 +0000 (13:34 +0100)]
correct pluralisation for "1 week"
Brian Fraser [Sat, 26 May 2012 00:46:19 +0000 (21:46 -0300)]
Test case for [perl #9391]
Craig A. Berry [Fri, 25 May 2012 22:56:55 +0000 (17:56 -0500)]
__DECCXX usually should do what __DECC does.
Unless __DECC was meant as the opposite of VAX C, which is not
C89-compliant and cannot build Perl.
Craig A. Berry [Fri, 25 May 2012 22:16:20 +0000 (17:16 -0500)]
Fix varying string struct for VMS's home-grown glob.
We were only using 4K, not 64K, and we were requesting longword
alignment but not providing a struct size that was a multiple of 4.
Zefram [Fri, 25 May 2012 21:25:21 +0000 (22:25 +0100)]
remove deprecated qw-as-parens behaviour
Leon Timmermans [Tue, 22 May 2012 14:58:26 +0000 (16:58 +0200)]
Block signals during fork (fixes RT#82580)
Zefram [Fri, 25 May 2012 20:19:20 +0000 (21:19 +0100)]
fix comparative Perl version numbers
Zefram [Fri, 25 May 2012 19:07:35 +0000 (20:07 +0100)]
perldelta updates
Zefram [Fri, 25 May 2012 17:56:45 +0000 (18:56 +0100)]
perldelta updates
Craig A. Berry [Fri, 25 May 2012 16:29:05 +0000 (11:29 -0500)]
Accumulate access warnings in stat.t.
On VMS, there is an additional warning that causes the warning of
interest to be lost and the test to fail. So append each warning
as we see it and then we'll find the access warning we're testing
for as long as it's in there somewhere.
Zefram [Fri, 25 May 2012 16:24:12 +0000 (17:24 +0100)]
perldelta updates
Zefram [Fri, 25 May 2012 16:23:48 +0000 (17:23 +0100)]
correct schedule for 5.17.0 release
Father Chrysostomos [Fri, 25 May 2012 16:12:30 +0000 (09:12 -0700)]
perldelta updates
Brian Fraser [Fri, 25 May 2012 05:44:20 +0000 (02:44 -0300)]
Fix for [perl #8931], call magic only once for join's first arg.
Karl Williamson [Fri, 25 May 2012 03:23:49 +0000 (21:23 -0600)]
Deprecate literal unescaped "{" in regexes.
We are deprecating literal left braces in regular expressions. The 5.16
delta announced that this is coming.
This commit causes a warning to be raised when a literal "{" is
encountered. However, it does not do this if the left brace is at the
beginning of a construct. Such a brace does not cause problems for us
for our future use of it for other purposes, as, for example in things
like \b{w}, and there were a large number of core tests that failed
without this condition.
I didn't mention this exception in the diagnostic. We may choose to
forbid it everywhere, and we certainly want to discourage its use
everywhere. But this commit gets the essential components in early in
5.17, and we can tighten it up later if we decide to.
Karl Williamson [Thu, 24 May 2012 17:49:31 +0000 (11:49 -0600)]
utf8.pm: pod: grammar, clarify
Craig A. Berry [Fri, 25 May 2012 02:47:45 +0000 (21:47 -0500)]
Fix a cast in vms/vms.c.
This is a follow-up to
c11536f52. Oddly. C++ was ok without the
"struct" but C wasn't.
Ricardo Signes [Fri, 25 May 2012 02:42:53 +0000 (22:42 -0400)]
add Version::Requirements as a known linkable-to lib
Otherwise, podcheck.t dies when we mention V::R in our perldelta!
Ricardo Signes [Fri, 25 May 2012 02:34:25 +0000 (22:34 -0400)]
perldelta: Version::Requirements has been removed
Ricardo Signes [Fri, 25 May 2012 02:17:32 +0000 (22:17 -0400)]
Revert "t/porting/checkcase.t should skip directories"
This reverts commit
f86fc3ff06fb5e5bae2719b5601eb7a094fe014b.
David and I had discussed this commit, along with some others on IRC,
and we felt the test was wrong and the commit was good. Unfortunately,
problems were reported only later, after Version-Requirements had
entered the core, so undoing the test would have required an
exception be made for lib/Version and lib/version conflicting.
Now that Version-Requirements has left the core, this test can be
restored.
Ricardo Signes [Fri, 25 May 2012 02:06:45 +0000 (22:06 -0400)]
remove Version-Requirements from core!
It has been replaced by CPAN::Meta::Requirements, which is just the
same code, renamed.
It was renamed (and now removed) to avoid conflicts on case-sensitive
filesystems between version::Internals and Version::Requirements.
Craig A. Berry [Fri, 25 May 2012 00:01:16 +0000 (19:01 -0500)]
Make configure.com ready for C++.
Building on Peter Prymmer's work from some years ago, this gets
the configuration process on VMS up to speed on the native C++
compiler. Quite a bit of it involves tweaking the configuration
probes to work under C++, plus a variety of other nits.
TODO: This should probably be made to work as -Dcc=cxx rather
than -Dusecxx as it does now, but it's still pretty experimental.
Craig A. Berry [Thu, 24 May 2012 22:47:39 +0000 (17:47 -0500)]
VMS C++ strerror prototype differences in perl.h.
The funny extra arguments to strerror are only there on VMS
when compiling with C, not C++.
On VMS, DONT_DECLARE_STD is synonymous with defined(__cplusplus).
Craig A. Berry [Thu, 24 May 2012 22:13:13 +0000 (17:13 -0500)]
File scope for VMS-specific #includes.
C++ requires #include directives to be at file scope, but we've
been lazy and haven't been doing that.
Craig A. Berry [Thu, 24 May 2012 21:58:22 +0000 (16:58 -0500)]
C++ification for vms/vmsish.h.
Its prototypes need extern "C" and the compiler messages that
cause trouble with DEC/Compaq/HP C++ are different from the ones
that cause trouble with C.
Craig A. Berry [Thu, 24 May 2012 21:54:28 +0000 (16:54 -0500)]
Fix up vms/vms.c for C++.
Almost all of this consists of casting the return values from
PerlMem_malloc, which inexpicably we weren't doing.
There are also some prototypes that have to be at file scope and
declare with extern "C".
And there was some embarrassing dead code in Perl_my_localtime
that the C++ compiler spotted.
Craig A. Berry [Thu, 24 May 2012 18:35:34 +0000 (13:35 -0500)]
Use the (START|END)_EXTERN_C macros.
We seem to use them everywhere else in core.
Karl Williamson [Thu, 24 May 2012 17:18:03 +0000 (11:18 -0600)]
handy.h: Fix definition of isOCTAL_A()
Commit
c2da0b36ccf7393a329af732fac4153ddf6ab42e changed this macro, and
created a syntax error. But it turns out that there were no current
calls to it in the Perl core. When I tried adding one, it showed the
failure.
Craig A. Berry [Sun, 6 May 2012 20:09:07 +0000 (15:09 -0500)]
The reentrant API should always have prototypes.
reentr.c always defines and exports its functions even when
USE_REENTRANT_API is not defined (though they'll be empty functions
in that case). In general we shouldn't be exporting functions
without providing prototypes for them, but specifically, when
compiling with C++, the prototype-less functions get their names
mangled. So the purpose of defining the functions when we aren't
using them (to have a consistent API) is defeated because no one
looking for those functions under their proper names would be able
to find them.
So this makes us stop hiding the prototypes when USE_REENTRANT_API
is not defined.
Craig A. Berry [Sun, 6 May 2012 13:50:43 +0000 (08:50 -0500)]
Unmangle mathoms under C++.
In order to actually provide binary compatibility, we have to
serve up these functions under the names they were known by
before making their way into mathoms.c. We've always done that
under C, but not C++.
Craig A. Berry [Thu, 24 May 2012 07:54:57 +0000 (00:54 -0700)]
[perl #112786] Fix build under clang++
A line of code in sv.c last modified at
<http://perl5.git.perl.org/perl.git/commit/
c6fb3f6e3e5160581b7?f=sv.c>
causes clang++ to fall down hard when building blead:
sv.c:13969:32: error: unexpected ':' in nested name specifier
CV * const cv = gv ? (CV *)gv : find_runcv(NULL);
^
::
sv.c:13969:34: error: no member named 'Perl_find_runcv' in 'gv'
CV * const cv = gv ? (CV *)gv : find_runcv(NULL);
~~~~ ^
./embed.h:137:24: note: expanded from macro 'find_runcv'
#define find_runcv(a) Perl_find_runcv(aTHX_ a)
^
sv.c:13969:50: error: expected ':'
CV * const cv = gv ? (CV *)gv : find_runcv(NULL);
^
:
sv.c:13969:21: note: to match this '?'
CV * const cv = gv ? (CV *)gv : find_runcv(NULL);
^
sv.c:13969:50: error: expected expression
CV * const cv = gv ? (CV *)gv : find_runcv(NULL);
^
14 warnings and 4 errors generated.
make: *** [sv.o] Error 1
clang++ seems to need only an extra set of parentheses to calm down
and let go of its anxieties.
[Committer’s note: Leon Timmermans points out that it's struct gv
that's confusing clang++. So a struct name used as a variable cannot
be followed by a colon.]
Karl Williamson [Thu, 24 May 2012 02:30:17 +0000 (20:30 -0600)]
Add perldelta for Unicode CCC132 fix
Father Chrysostomos [Thu, 24 May 2012 01:19:56 +0000 (18:19 -0700)]
Add another address for Ronald Kimball to checkAUTHORS.pl
Ronald J Kimball [Thu, 24 May 2012 01:17:16 +0000 (18:17 -0700)]
[perl #112604] perlre man page contains suspect example of recursion
Jim Avera wrote:
> This seems incorrect because the \s++ eats all white space without
> backtracking, preventing the following \s+ from matching.
> Thus the pattern always fails for any input.
It should be \s+ \+ \s+
Aristotle Pagaltzis [Thu, 24 May 2012 01:12:43 +0000 (18:12 -0700)]
[perl #112522] Mildly incorrect wording in "perldoc perlre"
Marcus Holland-Moritz [Wed, 23 May 2012 21:50:31 +0000 (14:50 -0700)]
[perl #60204] Unhelpful error message from unpack
Nigel Sandever said:
> The error message produced by the following snippets is very unhelpful:
>
> c:\>perl -wle"print unpack 'v/a*', qq[a]"
> '/' must follow a numeric type in unpack at -e line 1.
>
> c:\>perl -wle"print unpack 'v/a*', ''"
> '/' must follow a numeric type in unpack at -e line 1.
>
> c:\>perl -wle"print unpack 'v/a*', ' '"
> '/' must follow a numeric type in unpack at -e line 1.
The "problem" is that the data string is too short. But
unpack doesn't generate a warning (or croak) in this case
for simple patterns:
mhx@r2d2 $ perl -MData::Dumper -we'print Dumper([unpack "n", "a"])'
$VAR1 = [];
So, I'd say your code should just behave in exactly the
same way. No warning, no return values.
Father Chrysostomos [Wed, 23 May 2012 20:42:09 +0000 (13:42 -0700)]
Correct perldelta entry for fallback entry
Father Chrysostomos [Wed, 23 May 2012 20:17:17 +0000 (13:17 -0700)]
perldelta for PL_amagic_generation removal
Karl Williamson [Wed, 23 May 2012 23:14:36 +0000 (17:14 -0600)]
mktables: Handle typo in Unicode 6.1 data file
Unicode has published a correction to their data files for version 6.1.
This patch applies that correction.
Karl Williamson [Wed, 23 May 2012 23:01:11 +0000 (17:01 -0600)]
Revert "Fix mktables bug due to the previous overload fix"
mktables had unknowingly been relying on a bug in the overloading code.
That bug was fixed by commit
f041cf0f9c6469c41de8b73d5f7b426710c3ff8b.
Commit
5f9f83be9cdcd54449f7f40db078fe367d780475 is a minimal commit to
get mktables to pass its tests as a result of the fixed bug. However,
it did not address the underlying problem, which doesn't show up in the
typical tests, but does occur when tracing is added or things go wrong
and mktables tries to output any of a number of messages, which fail
because there is no ".=" operator. A previous commit added the proper
overloaded ".=", and so this one is no longer needed, and would be
confusing to someone who doesn't know the history.
Karl Williamson [Thu, 19 Apr 2012 18:25:08 +0000 (12:25 -0600)]
mktables: Add sanity check
Since mktables works only on Unicode code points so far, a range outside
that space is probably erroneous. Raise a warning
Karl Williamson [Mon, 16 Apr 2012 17:32:43 +0000 (11:32 -0600)]
mktables: Add overloaded .=
This was automatically getting generated due to a bug in perl which
ignored fallback=>0, but that has been fixed by commit
f041cf0f9c6469c41de8b73d5f7b426710c3ff8b, so we have to have our own
operator.
Karl Williamson [Mon, 16 Apr 2012 17:31:50 +0000 (11:31 -0600)]
mktables: Add error check
+= is not a commutative operator, and so the overloaded version should
not accept the parameters being swapped.
Karl Williamson [Mon, 16 Apr 2012 17:28:20 +0000 (11:28 -0600)]
mktables: Add overloaded '+='
This was automatically generated before, in spite of fallback => 0, but
that has now been fixed by commit
f041cf0f9c6469c41de8b73d5f7b426710c3ff8b. However, that change caused
another overloaded += to be used with the parameters swapped, resulting
in the table generated for Gc=Cs (the surrogates) to be wrong. This
creates the proper overload.
Karl Williamson [Tue, 27 Mar 2012 04:20:59 +0000 (22:20 -0600)]
podcheck.t: Try harder to avoid transitory failure
It may be that a file that looks like a pod is transitory. podcheck.t
catches and handles some of these, but there are cases where it doesn't
catch these. This commit adds code to try harder to detect such
instances and recover properly.
I know of two instances in the months since this code has been in
service where this has happened, so it's not a common occurrence, and
re-running it makes the failure go away. Still, if it can be easily
avoided, do so.
Karl Williamson [Tue, 27 Mar 2012 04:18:01 +0000 (22:18 -0600)]
podcheck.t: Add label to 'next' stmts for clarity
Rafael Garcia-Suarez [Wed, 23 May 2012 13:53:31 +0000 (15:53 +0200)]
Merge branch 'rgs/overload' into blead
Father Chrysostomos [Wed, 23 May 2012 08:05:20 +0000 (01:05 -0700)]
[perl #113050] Put fallback back under "()"
Unfortunately, there is code all over CPAN that assumes fallback is
stored under the "()" stash entry. And that code also assumes that
the overloadedness flag (the existence of the CV) is in the same spot.
So much for encapsulation.
This commit changes overloading itself to use a different key, "((",
while having it search for "()" first, and then "((" only if "()" is
not found, to preserve compatibility with encapsulation-breaking code.
So the "((" key will only be used by gv.c if there is no fallback
value specified at all.
Father Chrysostomos [Wed, 23 May 2012 06:54:39 +0000 (23:54 -0700)]
Increase $ExtUtils::ParseXS::Utilities::VERSION to 3.17
Father Chrysostomos [Wed, 23 May 2012 05:46:27 +0000 (22:46 -0700)]
Increase $ExtUtils::ParseXS::VERSION to 3.17
Father Chrysostomos [Wed, 23 May 2012 05:46:05 +0000 (22:46 -0700)]
ParseXS.pm: Only inc PL_amagic_generation before 5.9
Originally, overload would not oven be checked for if
amagic_generation was 0, so it was necessary to do
PL_amagic_generation++, in case this was the first class to have over-
loading. Ever since perl-5.8.0-87-g439cb1c, PL_amagic_generation++
has been unnecessary, since the boot code for version objects incre-
ments it. Furthermore, newXS was already doing PL_sub_generation++
before that, and now does mro_method_changed_in. The code for check-
ing the staleness of the overload tables has always checked
sub_generation (and, later, the stash-specific generation numbers).
Father Chrysostomos [Wed, 23 May 2012 05:22:32 +0000 (22:22 -0700)]
Excise PL_amagic_generation
The core is not using it any more. Every CPAN module that increments
it also does newXS, which triggers mro_method_changed_in, which is
sufficient; so nothing will break.
So, to keep those modules compiling, PL_amagic_generation is now an
alias to PL_na outside the core.
Father Chrysostomos [Wed, 23 May 2012 03:46:52 +0000 (20:46 -0700)]
op.c: One less func call for newXS
newXS calls newXS_flags, which calls newXS_len_flags. This commit
makes newXS call the underlying function directly.
Father Chrysostomos [Wed, 23 May 2012 03:41:12 +0000 (20:41 -0700)]
perlfunc: long lines
Father Chrysostomos [Wed, 23 May 2012 03:10:47 +0000 (20:10 -0700)]
Add Igor Zaytsev to AUTHORS
Igor Zaytsev [Wed, 23 May 2012 01:02:02 +0000 (18:02 -0700)]
[perl #111918] Fix thawing seen objects in STORABLE_attach hook
Before any thaw hook is called Storable creates a new blessed object that
is stored in a seen cache and then is provided to the hook. That is fine
for STORABLE_thaw which fills in this object and returns it. STORABLE_attach
on the other hand can create entirely new object by itself, so one
memoized before should be thrown out to be replaced by that new object.
Steffen Mueller [Tue, 22 May 2012 21:04:06 +0000 (23:04 +0200)]
Make CV * typemap entry support overloading
See RT #96872.
Eric Brine [Tue, 22 May 2012 19:29:48 +0000 (15:29 -0400)]
Purported equivalency isn't.
Reini Urban [Tue, 22 May 2012 15:57:03 +0000 (10:57 -0500)]
replace B::COP::stashflags by B::COP::stashlen
6379d4a9a (between 5.15.9 and 5.16.0) broke B::COP::stashflags which was added
in 5.15.4.
Rafael Garcia-Suarez [Tue, 22 May 2012 15:23:20 +0000 (17:23 +0200)]
Fix mktables bug due to the previous overload fix
Due to the previous patch, perl can't generate the operator for .= in
package Property anymore (because fallback is '0' in that package), so
we need to work around that; this patch implements the least intrusive
workaround possible.
Robin Barker (via RT) [Thu, 1 Mar 2012 15:20:33 +0000 (07:20 -0800)]
refactor macro to avoid compiler warning in regcomp.c
The compiler warning in regcomp.c (as noted in recent comment)
can be avoided by refactoring DO_POSIX_LATIN1_ONLY_KNOWN
to separate the case where sourcelist==l1_sourcelist
The committer changed the name of the new macro so he could understand
it better, and added a couple comments
Karl Williamson [Mon, 21 May 2012 03:45:15 +0000 (21:45 -0600)]
perlebcdic: make verbatim line fit in 79 cols
Karl Williamson [Sun, 20 May 2012 22:22:44 +0000 (16:22 -0600)]
regen/mk_invlists.pl: Fail if inversion list not found
This is instead of silently returning nothing.
Karl Williamson [Sun, 20 May 2012 21:52:13 +0000 (15:52 -0600)]
perlebcdic: Narrow table to fit in 79 columns
This uses the abbreviations for control characters available officially
in Unicode 6.1, instead of the much longer names, thus enabling this
table to be narrowed. With some space changes, it will fit in 79
columns. The differences look large, but most go away under 'diff -b'.
The recipes are changed to correspond.
Karl Williamson [Sun, 20 May 2012 21:50:25 +0000 (15:50 -0600)]
perlebcdic: Add a few commas for clarity