[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gawk] Command-line -L option always consumes the next token, in
From: |
Manuel Collado |
Subject: |
Re: [bug-gawk] Command-line -L option always consumes the next token, instead of an optional one |
Date: |
Sun, 24 Dec 2017 18:24:41 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 |
Sorry. Forgot to say:
1.- Reported by Kenny McCormack on comp.lang.awk
2.- Tested with Windows-10 + Cygwin-64 + gawk-4.2.0a
3.- Simple test:
$ ./gawk.exe -L fatal -f xxx.awk
gawk: fatal: can't open source file `xxx.awk' for reading (No such file
or directory)
--> Ok
$ ./gawk.exe -L -f xxx.awk
gawk: cmd. line:1: xxx.awk
gawk: cmd. line:1: ^ syntax error
--> Wrong, behaves like:
$ ./gawk.exe --lint=-f xxx.awk
gawk: cmd. line:1: xxx.awk
gawk: cmd. line:1: ^ syntax error
Regards.
El 24/12/2017 a las 17:16, Manuel Collado escribió:
Unlike --lint, -L always requires an option argument. The bug is
probably in:
main.c:1446 const char *optlist =
"+F:f:v:W;bcCd::D::e:E:ghi:l:L:nNo::Op::MPrSstVYZ:";
should be:
main.c:1446 const char *optlist =
"+F:f:v:W;bcCd::D::e:E:ghi:l:L::nNo::Op::MPrSstVYZ:";
Hope this helps.
--
Manuel Collado - http://lml.ls.fi.upm.es/~mcollado