@@ -23,7 +23,7 @@ Files patched: README
23
23
NETaa13033: goto pushed a bogus scope on the context stack.
24
24
From: Steve Vinoski
25
25
Files patched: pp_ctl.c
26
- The goto operator pushed an extra bogus scope onto the context stack. (This
26
+ The goto operator pushed an extra bogus scope onto the context stack. (This
27
27
often didn't matter, since many things pop extra unrecognized scopes off.)
28
28
29
29
NETaa13034: tried to get valid pointer from undef.
@@ -146,7 +146,7 @@ Files patched: op.c
146
146
outside the eval only partially took into consideration that there
147
147
might be extra debugger subroutine frames that shouldn't be used, and
148
148
ended up comparing the wrong statement sequence number to the range of
149
- valid sequence numbers for the scope of the lexical variable. (There
149
+ valid sequence numbers for the scope of the lexical variable. (There
150
150
was also a bug fixed in passing that caused the scope of lexical to go
151
151
clear to the end of the subroutine even if it was within an inner block.)
152
152
@@ -180,15 +180,15 @@ Files patched: pod/perlsyn.pod
180
180
NETaa13164: the dot detector for the end of formats was over-rambunctious.
181
181
From: John Stoffel
182
182
Files patched: toke.c
183
- The dot detector for the end of formats was over-rambunctious. It would
183
+ The dot detector for the end of formats was over-rambunctious. It would
184
184
pick up any dot that didn't have a space in front of it.
185
185
186
186
NETaa13165: do {} while 1 never linked outer block into next chain.
187
187
From: Gisle Aas
188
188
Files patched: op.c
189
189
When the conditional of do {} while 1; was optimized away, it confused the
190
190
postfix order construction so that the block that ordinarily sits around the
191
- whole loop was never executed. So when the loop tried to unstack between
191
+ whole loop was never executed. So when the loop tried to unstack between
192
192
iterations, it got the wrong context, and blew away the lexical variables
193
193
of the outer scope. Fixed it by introducing a NULL opcode that will be
194
194
optimized away later.
@@ -315,7 +315,7 @@ NETaa13181: m//g didn't keep track of whether previous match matched null.
315
315
From: "philippe.verdret"
316
316
Files patched: mg.h pp_hot.c
317
317
A pattern isn't allowed to match a null string in the same place twice in
318
- a row. m//g wasn't keeping track of whether the previous match matched
318
+ a row. m//g wasn't keeping track of whether the previous match matched
319
319
the null string.
320
320
321
321
NETaa13182: now includes whitespace as a regexp metacharacter.
374
374
Files patched: mg.c
375
375
Since there was no regexp prior to the "use", it was returning whatever the
376
376
last successful match was within the "use", because there was no current
377
- regexp, so it treated it as a normal variable. It now returns undef.
377
+ regexp, so it treated it as a normal variable. It now returns undef.
378
378
379
379
NETaa13195: semop had one S too many.
380
380
From: Joachim Huober
@@ -389,7 +389,7 @@ Files patched: toke.c
389
389
NETaa13197: changed implicit -> message to be more understandable.
390
390
From: Bruce Barnett
391
391
Files patched: op.c pod/perldiag.pod
392
- I changed the error message to be more understandable. It now says
392
+ I changed the error message to be more understandable. It now says
393
393
394
394
Can't use subscript on sort...
395
395
@@ -513,7 +513,7 @@ NETaa13342: grep and map with block would enter block but never leave it.
513
513
From: Ian Phillipps
514
514
Files patched: op.c
515
515
The compiler use some sort-checking code to handle the arguments of
516
- grep and map. Unfortunately, this wiped out the block exit opcode while
516
+ grep and map. Unfortunately, this wiped out the block exit opcode while
517
517
leaving the block entry opcode. This doesn't matter to sort, but did
518
518
matter to grep and map. It now leave the block entry intact.
519
519
@@ -536,8 +536,8 @@ Files patched: gv.c
536
536
537
537
use strict;
538
538
sub foo {
539
- local(*IN);
540
- open(IN,"file");
539
+ local(*IN);
540
+ open(IN,"file");
541
541
}
542
542
543
543
@@ -554,7 +554,7 @@ Files patched: av.c
554
554
NETaa13349: sort sub accumulated save stack entries
555
555
From: David Filo
556
556
Files patched: pp_ctl.c
557
- COMMON only gets set if assigning to @_, which is reasonable. Most of the
557
+ COMMON only gets set if assigning to @_, which is reasonable. Most of the
558
558
problem was a memory leak.
559
559
560
560
NETaa13351: didn't treat indirect filehandles as references.
@@ -621,7 +621,7 @@ Files patched: toke.c
621
621
untainted. Unfortunately, the scope removal optimization for very
622
622
short blocks removed the statementhood of statements that were
623
623
attempting to read $1 as an untainted value, with the effect that $1
624
- appeared to be tainted anyway. The optimization is now disabled when
624
+ appeared to be tainted anyway. The optimization is now disabled when
625
625
tainting and the block contains $1 (or equivalent).
626
626
627
627
NETaa13366: fixed this a better way in toke.c.
@@ -666,7 +666,7 @@ NETaa13370: some code assumed SvCUR was of type int.
666
666
From: Spider Boardman
667
667
Files patched: pp_sys.c
668
668
Did something similar to the proposed patch. I also fixed the problem that
669
- it assumed the type of SvCUR was int. And fixed get{peer,sock}name the
669
+ it assumed the type of SvCUR was int. And fixed get{peer,sock}name the
670
670
same way.
671
671
672
672
NETaa13375: sometimes dontbother wasn't added back into strend.
@@ -994,7 +994,7 @@ Files patched: op.c pod/perlop.pod
994
994
NETaa13500: needed DESTROY in FileHandle
995
995
From: Tim Bunce
996
996
Files patched: ext/POSIX/POSIX.pm
997
- Added DESTROY method. Also fixed ungensym to use POSIX:: instead of _POSIX.
997
+ Added DESTROY method. Also fixed ungensym to use POSIX:: instead of _POSIX.
998
998
Removed ungensym from close method, since DESTROY should do that now.
999
999
1000
1000
NETaa13502: now complains if you use local on a lexical variable
@@ -1013,7 +1013,7 @@ From: William Setzer
1013
1013
Files patched: op.c
1014
1014
When a lexical variable is declared, introduction is delayed until
1015
1015
the start of the next statement, so that any initialization code runs
1016
- outside the scope of the new variable. Thus,
1016
+ outside the scope of the new variable. Thus,
1017
1017
1018
1018
my $y = 3;
1019
1019
my $y = $y;
@@ -1054,7 +1054,7 @@ Files patched: embed.h
1054
1054
NETaa13525: random cleanup
1055
1055
Files patched: MANIFEST Todo cop.h lib/TieHash.pm lib/perl5db.pl opcode.h patchlevel.h pod/perldata.pod pod/perlsub.pod t/op/ref.t toke.c
1056
1056
1057
- NETaa13525: random cleanup
1057
+ NETaa13525: random cleanup
1058
1058
Files patched: pp_ctl.c util.c
1059
1059
1060
1060
NETaa13527: File::Find needed to export $name and $dir
@@ -1149,7 +1149,7 @@ NETaa13589: return was enforcing list context on its arguments
1149
1149
From: Tim Freeman
1150
1150
Files patched: opcode.pl
1151
1151
A return was being treated like a normal list operator, in that it was
1152
- setting list context on its arguments. This was bogus.
1152
+ setting list context on its arguments. This was bogus.
1153
1153
1154
1154
NETaa13591: POSIX::creat used wrong argument
1155
1155
From: Paul Marquess
@@ -1232,7 +1232,7 @@ Files patched: lib/Exporter.pm
1232
1232
like an adjunct. Also added an export_tags routine. The keys in the
1233
1233
%EXPORT_TAGS hash no longer use colons, to make the initializers prettier.
1234
1234
1235
- NETaa13687: new Exporter.pm
1235
+ NETaa13687: new Exporter.pm
1236
1236
Files patched: ext/POSIX/POSIX.pm
1237
1237
(same)
1238
1238
0 commit comments