On Mie. Mar. 14 11:46:38 2007, [EMAIL PROTECTED] wrote:
> I keep getting a test failure on t/op/stringu.t with test 25 on 
> ppc-darwin(and likely all big endian systems with icu installed).  
> Parrot outputs "\x00A\x00B" when the test expects "A\x00B\x00" to be 
> printed.

Is this still a problem? Recent changes makes that the expected output
of a test like that is utf8 and then endianess independent, but don't
know if there are others with utf16 or ucs2 output.

Reply via email to