bug-gawk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] Continuation Character not recognized in GAWK 4.1


From: Rush, Scott (CS COE)
Subject: Re: [bug-gawk] Continuation Character not recognized in GAWK 4.1
Date: Tue, 24 Feb 2015 20:44:27 +0000

Just to be clear...the situation where the continuation character is not being 
seen was with the 64-bit version of GAWK I was trying to use. You have solved 
my issue of getting GAWK to work on my new Win7 64-bit PC. So, I no longer have 
that continuation character issue since I'm using the same version of GAWK now 
on my new PC as I was using on my old PC.

So, be certain you are not wasting your time since the continuation character 
issue I had was with that unofficial version of GAWK.

-----Original Message-----
From: Eli Zaretskii [mailto:address@hidden 
Sent: Tuesday, February 24, 2015 1:21 PM
To: Aharon Robbins
Cc: Rush, Scott (CS COE); address@hidden
Subject: Re: [bug-gawk] Continuation Character not recognized in GAWK 4.1

> From: Aharon Robbins <address@hidden>
> Date: Tue, 24 Feb 2015 22:01:52 +0200
> 
> > awk: test:2:  printf("Hello \
> > awk: test:2:         ^ unterminated string
> > awk: test:2:  printf("Hello \
> > awk: test:2:         ^ syntax error
> 
> This is a separate issue from 32/64 windows/not-windows. This occurs 
> because some of the gawk code understands CR-LF files and some of it 
> does not. The source code patch below fixes the problem, so it will be 
> fixed "for real" when I release 4.1.2.

What will happen with that fix if you have a lone \r character?

And anyway, Gawk by default reads in text mode, so the \r\n pairs should be 
seen as a single \n character.  Are you sure this is the cause of the problem?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]