----> Does this mean nawk does not fully comply with the standard ?What I have not noticed before submitting the patch, is that both nawk and gawk behaved differently depending on quoting type. With single-quotes and before your recent changes, we got:
$ nawk -v x='abc\
> def' 'BEGIN { print x }'
abc
def
$ gawk (--posix|--traditional|<nothing>) -v x='abc\
> def' 'BEGIN {print x}'
abc\def
With double-quotes (the first newline is ignored by the shell as stated by the standard,
section 2.2.1 and
2.2.3)
and before your recent changes, we got:
$ nawk -v x="abc\
>
> def" 'BEGIN { print x }'
nawk: newline in string abc
def... at source line 1
$ gawk (--posix|--traditional|<nothing>) -v x="abc\
>
> def" 'BEGIN {print x}'
abc
def
I tried to make gawk --traditional mimic the behavior of nawk (with respect to double-quoting) but, as you stated, I got gawk --traditional to be more restrictive than nawk (with respect to single-quoting).
I just had a look to your (massive) changes. I will test and experiment today.
Thank you very much for your work.
Best regards,
Samy Mahmoudi