Re: bug in cygwin perl

2020-10-26 Thread Achim Gratz
L A Walsh writes: > I'm using perl 5.26. There's your problem… $ perl -e 'use charnames qw{:full};' $ perl --version This is perl 5, version 30, subversion 3 (v5.30.3) built for x86_64-cygwin-threads-multi (with 7 registered patches, see perl -V for more detail) Regards, Achim. -- +<[Q+ Mat

bug in cygwin perl

2020-10-25 Thread L A Walsh
I'm using perl 5.26. The following perl-lib function fails. perl -e 'use charnames qw{:full};' Undefined subroutine utf8::SWASHNEW called at /usr/share/perl5/5.26/_charnames.p m line 176. Com

Re: bug in Cygwin perl 5.6.1?

2002-02-04 Thread Gerrit P. Haase
Hallo Rhet, 04.02.2002, 16:09, es wurde gemailt: > Gerrit P. Haase wrote: >>Hmmm, I'm still confused a little. Isn't '010' as TRUE as '011'? [detailed analysis] > Hope that helps. Regards, Yes, now I see;) Thank you very much for the detailed explanation. -- Gerrit -- Unsubscribe info:

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-04 Thread Dr. Volker Zell
> "Volker" == Volker Zell writes: > "Christopher" == Christopher Faylor <[EMAIL PROTECTED]> writes: Christopher> perl -e 'print $^S || 0, "\n";eval {print $^S || 0, "\n"}; print $^S || 0, "\n";' Christopher> This should print: Christopher> 0 Christopher> 1 Christop

Re: bug in cygwin perl 5.6.1?

2002-02-04 Thread Dr. Volker Zell
> "Christopher" == Christopher Faylor <[EMAIL PROTECTED]> writes: Christopher> perl -e 'print $^S || 0, "\n";eval {print $^S || 0, "\n"}; print $^S || 0, "\n";' Christopher> This should print: Christopher> 0 Christopher> 1 Christopher> 0 Christopher> Instead, it pr

Re: bug in cygwin perl 5.6.1?

2002-02-03 Thread Christopher Faylor
On Sun, Feb 03, 2002 at 10:03:36PM +0100, Gerrit P. Haase wrote: >Am 2 Feb 2002 um 17:58 hat Rhet Turnbull geschrieben: > >>Gerrit P. Haase wrote: >>> Why? Where is docu about this? >> >>The perl documentation for $^S in the perlvar manpage states: >> >>$^S Current state of the interpreter.

Re: bug in Cygwin perl 5.6.1?

2002-02-03 Thread Gerrit P. Haase
Am 2 Feb 2002 um 17:58 hat Rhet Turnbull geschrieben: >Gerrit P. Haase wrote: >> Why? Where is docu about this? > >The perl documentation for $^S in the perlvar manpage states: > >$^S Current state of the interpreter. Undefined if >parsing of the current module/eval is not finished

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-02-02 Thread Gerrit P. Haase
Am 31 Jan 2002 um 9:21 hat Rhet Turnbull geschrieben: >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' Why? Where is docu about this? Thanks Gerrit >However, on Cygwin perl 5.6.1

Re: bug in Cygwin perl 5.6.1?

2002-01-31 Thread Rhet Turnbull
FYI, I reported the perl bug mentioned on the Cygwin mailing list earlier today to perlbug and they've reported back that it is a known bug and that it'll be fixed in the next version (5.6.2). Regards, Rhet Original Message Follows From: Mike Guy Reply-To: To: [EMAIL PROTECTED],[EMAI

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