bug with rmdir: Perl 5.6.1/Cygwin 1.3.9

2002-03-04 Thread Rhet Turnbull
I'm sending this to both perlbug and cygwin mailing lists since I'm not sure if it's a perl or cygwin problem. Regards, Rhet Turnbull To: [EMAIL PROTECTED] Subject: Attempt to rmdir current directory under Cygwin Perl 5.6.1 causes perl to abort without an error Reply-To: [

Re: bug in Cygwin perl 5.6.1?

2002-02-04 Thread Rhet Turnbull
Regards, --Rhet Original Message Follows---- From: "Gerrit P. Haase" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: "Rhet Turnbull" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> Subject: Re: bug in Cygwin perl 5.6.1? Date: Sun, 3 Feb 2002

Re: bug in Cygwin perl 5.6.1?

2002-02-02 Thread Rhet Turnbull
ed in next release. Regards, --Rhet - Original Message - From: "Gerrit P. Haase" <[EMAIL PROTECTED]> To: "Rhet Turnbull" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, February 02, 2002 5:30 PM Subject: Re: bug in Cyg

Re: bug in Cygwin perl 5.6.1?

2002-01-31 Thread Rhet Turnbull
PROTECTED],[EMAIL PROTECTED] Subject: Re: [ID 20020131.003] $^S incorrect after eval in Cygwin Perl 5.6.1 Date: Thu, 31 Jan 2002 18:05:45 +0000 Rhet Turnbull <[EMAIL PROTECTED]> wrote > $^S seems to be incorrectly set *after* an eval block > when using Cygwin perl 5.6.1-2. Yes - known b

bug in Cygwin perl 5.6.1?

2002-01-31 Thread Rhet Turnbull
There seems to be a bug in Cygwin's perl (5.6.1). The following code: perl -e 'print $^S || 0;eval {print $^S || 0}; print $^S || 0;' should produce '010' However, on Cygwin perl 5.6.1, it produces 011. This means that perl incorrectly thinks it's in an eval block when it's not. I've checked