Re: [perl #25251] Encode::decode trashes input parameter since Encode 0.96

2004-02-08 Thread Nick Ing-Simmons
Andreas J Koenig [EMAIL PROTECTED] writes: - decode($octets [,$check]) MUST return the string that $octets represents. If $check is true, it SHOULD modify $octets in place to remove the converted part (i.e. the whole sequence unless there is an error). If perlio_ok()

Re: Bug in Encode/perlio

2004-02-08 Thread Nick Ing-Simmons
Matt Sergeant [EMAIL PROTECTED] writes: On 25 Jan 2004, at 6:54, SADAHIRO Tomoyuki wrote: Your file is encoded in Shift-JIS. Yes I know - but the data comes from an external source and lies about the encoding. Perl should never hang in an infinite loop like this. \perl -e print chr 0x41 |

Re: Whither 5.6.3?

2004-02-08 Thread Yitzchak Scott-Thoennes
On Sun, Feb 01, 2004 at 01:59:00AM +, Dave Mitchell [EMAIL PROTECTED] wrote: This patch threw up quite a lot of problems in the test suite, which is an indication that there's a *lot* of code out there about to get noisy. Here is a list of the major ones, along with sample snippets of code

Re: Are perl_parse and perl_run thread safe?

2004-02-08 Thread Nick Ing-Simmons
Aditya Prasad [EMAIL PROTECTED] writes: Hello, I wanted to know if the functions perl_parse and perl_run are thread safe. In other words, i am using multiple perl interpreters allocated in different threads and these threads will be running parallely. I noticed that when one of the threads was