summaryrefslogtreecommitdiff
path: root/Porting/todo.pod
diff options
context:
space:
mode:
authorHugo van der Sanden <hv@crypt.org>2020-09-15 15:26:51 +0100
committerHugo van der Sanden <hv@crypt.org>2020-09-15 15:26:51 +0100
commit9c705b6a737887a4da01ff0f1aee235dccb1ef26 (patch)
treefe154e09af1a6f6f042c8b4fdba70d0b410add9b /Porting/todo.pod
parent3447587c61a336330237bd97108b38d8373c3660 (diff)
downloadperl-9c705b6a737887a4da01ff0f1aee235dccb1ef26.tar.gz
Update a couple of RT references in todo.pod
Diffstat (limited to 'Porting/todo.pod')
-rw-r--r--Porting/todo.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/Porting/todo.pod b/Porting/todo.pod
index 37ed3a811e..c44625720d 100644
--- a/Porting/todo.pod
+++ b/Porting/todo.pod
@@ -760,7 +760,7 @@ L</"Virtualize operating system access">.
Currently the %ENV entries are always byte strings.
See L</"Virtualize operating system access">.
-(See RT ticket #113536 for information on Win32's handling of %ENV,
+(See github issue gh12161 for information on Win32's handling of %ENV,
which was fixed to work with native ANSI codepage characters in the
environment, but still doesn't work with other characters outside of
that codepage present in the environment.)
@@ -943,8 +943,8 @@ This does not:
$ perl -we 'my $pie = 42'
Logically all lexicals used only once should warn, if the user asks for
-warnings. An unworked RT ticket (#5087) has been open for almost seven
-years for this discrepancy.
+warnings. An unworked ticket (gh3073) was open for many years for this
+discrepancy.
=head2 state variable initialization in list context