Re: [PATCH] enable locale-induced UTF-8 I/O only if explicitly asked (Was: Re: [perl #19743] implicit utf8ification causes action-at-distance bugs)

Op een zonnige winterdag (Tuesday 14 January 2003 16:49), schreef Jarkko 
Hietaniemi:

[snip]
> In a perverse way going explicit is bad news since the implicit
> UTF-8-ification has certainly shaken many evil bugs out of the
> 5.8.0 tree (the B0B bug comes to mind, for example).  Maybe for
> those platforms that have UTF-8 locales a new column of smoke
> testing (with env PERL_UTF8_LOCALE=1 LC_ALL=xx_YY.UTF-8) would
> be in order.

I've been thinking about this and did some testing (on SuSE 8.0 with heaps of 
locales).

1) perl-5.8.x will not build for me with PERL_UTF8_LOCALE=1 LC_ALL=en_US.utf8

        $ cd perl-5.8.x
	$ PERL_UTF8_LOCALE=1 LC_ALL=en_US.utf8 ./Configure -des -Dusedevel
	$ PERL_UTF8_LOCALE=1 LC_ALL=en_US.utf8 make

Dies on building Digest::MD5

2) perl-current with those locale settings gives:

        $ cd t
	$ PERL_UTF8_LOCALE=1 LC_ALL=en_US.utf8 ./perl harness
Failed Test            Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
../ext/Encode/t/CJKT.t   21  5376    42   21  50.00%  1-3 7-9 13-15 19-21
                                                      25-27 31-33 37-39
49 tests and 413 subtests skipped.
Failed 1/754 test scripts, 99.87% okay. 21/70272 subtests failed, 99.97% okay.

3) Do we have enough data if we *only* run 'make test' with locale settings?
4) Shouldn't we test both ':stdio' and ':perlio' layers under locale?
5) If not, is ':perlio' the one to choose or should we just use an empty 
$ENV{PERLIO}?

Ready to hack on the Test::Smoke suite, I would like to have this in 1.17

Good luck,

Abe
-- 
 I think this requires more thought, therefore
I'm excising the "promise" from perldelta and replacing it with more
non-committal mumbling.
                                   -- Jarkko Hietaniemi on p5p @ 2002-05-27