FAQ

On Sun, Apr 06, 2003 at 12:28:16AM +0900, Dan Kogai wrote:
This is HOW IT WAS USED TO BE until Encode 1.92. But Enache found this
causes problem with FreeBSD4+thread so he first deleted "close STDOUT"
FreeBSD 5.0 / user-threads (libc_r.so) in fact. According to
Jos Boumans, it works fine with FreeBSD 4.x. And probably using
the rfork-based linuxthreads or the new libthr will make it
work fine too ( I'll try the latest when I have enough time )
but I told it it would break Win32 because Win32 does not allow you to
unlink open files.
Should make it a TODO test be politically correct ?
That will give the impression that the failure is related to Encode
which in fact it isn't.

or just this:
-----------------------------------------------------------------------
--- /arc/perl/ext/Encode/t/enc_module.t Wed Apr 2 08:55:40 2003
+++ perl/ext/Encode/t/enc_module.t Sat Apr 5 21:42:08 2003
@@ -38,7 +38,8 @@
print $obj->str, "\n";
$obj->set("¥Æ¥¹¥Èʸ»úÎó");
print $obj->str, "\n";
-close STDOUT;
+close STDOUT unless $^O eq 'freebsd';
+ # weird bug in FreeBSD5.0/user-threads (libc_r.so)

my $cmp = compare_text($file0, $file1);
is($cmp, 0, "encoding vs. STDOUT");
-----------------------------------------------------------------------

Regards
Adi

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 3 | next ›
Discussion Overview
groupperl5-porters @
categoriesperl
postedApr 5, '03 at 3:28p
activeApr 6, '03 at 4:06p
posts3
users3
websiteperl.org

People

Translate

site design / logo © 2022 Grokbase