Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gerrit P. Haase" Organization: Esse keine toten Tiere To: Rhet Turnbull , rhetlist AT yahoo DOT com, cygwin AT cygwin DOT com Date: Sat, 2 Feb 2002 23:30:40 +0100 MIME-Version: 1.0 Subject: Re: bug in Cygwin perl 5.6.1? Reply-to: gerrit AT familiehaase DOT de Message-ID: <3C5C76A0.24107.25783F5@localhost> In-reply-to: <20020131172146.7797.qmail@web14007.mail.yahoo.com> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Sender: 320081107336-0001 AT t-dialin DOT net 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, it produces 011. This >means that perl incorrectly thinks it's in an eval >block when it's not. I've checked this on perl v5.6.1 >for other platforms (including Win32) and it seems to >work fine. -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/