DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=CbF
	bIfkSVx/77v8kr5vCkyfQ3iBgfzRFuy5kjpB7FHAamfvyN8T5HsMe0eY9uNfxPJq
	02AowX2zD6xwQ2Y+a+T6DehawSyHIE/wR+APCHNklN78MB/QNjaxIEm85qVk2FAO
	RPAdePIqhfyzsEUYmuGXEYm0Yrsh4Cc4F/iNRrPI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Jannick" <thirdedition@gmx.net>
To: <cygwin@cygwin.com>
Subject: gawk 4.1.4: CR separate char for CRLF files
Date: Wed, 9 Aug 2017 01:15:08 +0200
Message-ID: <004401d3109c$2dcb09e0$89611da0$@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear All,

the current version 4.1.4 of gawk appears to unpleasantly treat CR for CRLF
files, i.e. CR is not gracefully swallowed, but is a separate character.

This makes some, if not all, of the scripts we are working with here
useless, unless the input files are converted to LF which certainly is not
feasible. IIRC the issue did not show up some versions back. 

Is this a bug - or am I missing something here?

Thanks,
J. - living on Win10


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple