Open GoogleCodeExporter opened 9 years ago
Original comment by todd.e.rinaldo
on 31 Jan 2014 at 12:38
This is related to the magic names STDOUT and STDERR, which do not yet store
the attached format.
perlcc -r -e 'BEGIN { eval qq{format STD =\n.} } print "ok\n" if
ref(*STD{FORMAT}) eq "FORMAT";'
works fine
Original comment by reini.urban
on 31 Jan 2014 at 6:26
Issue 286 has been merged into this issue.
Original comment by reini.urban
on 31 Jan 2014 at 6:26
Merged all format testcases into t/issue238.t
Fixed in 1.43_05 with commit ee98e2245a489a241315056ffb3e01e7eb697ae6
Author: Reini Urban <rurban@cpanel.net>
Date: Fri Jan 31 12:50:11 2014 -0600
1.43_05: fix format STDOUT/STDERR
added all format testcases to t/issue238.t
Original comment by reini.urban
on 31 Jan 2014 at 7:03
Not fixed and I have ee98e2245a489a241315056ffb3e01e7eb697ae6 in my history.
Original comment by todd.e.rinaldo
on 31 Jan 2014 at 11:24
What testcase is broken exactly?
I added all known failures to t/issue238 and they all pass.
#277,#284,#283,#239,#285,#238
format STDOUT and STDERR are now stored correctly
Original comment by reini.urban
on 1 Feb 2014 at 6:37
note fixed with ee98e2245a489a241315056ffb3e01e7eb697ae6
> perlcc -r -e 'BEGIN { eval qq{format STDERR =\n.} } print "ok\n" if
ref(*STDERR{FORMAT}) eq "FORMAT";'
> perlcc -O3 -r -e 'BEGIN { eval qq{format STDERR =\n.} } print "ok\n" if
ref(*STDERR{FORMAT}) eq "FORMAT";'
Original comment by nicolas....@gmail.com
on 6 Feb 2014 at 8:23
Original comment by reini.urban
on 11 Jun 2014 at 11:20
Original comment by reini.urban
on 11 Jun 2014 at 11:24
Original issue reported on code.google.com by
nicolas....@gmail.com
on 30 Jan 2014 at 10:25