Searched hist:"62 addaefc90626acb3e1950378964fe08c2c3ef5" (Results 1 – 3 of 3) sorted by relevance
| /freebsd/bin/sh/ |
| H A D | parser.h | diff 62addaefc90626acb3e1950378964fe08c2c3ef5 Sun Nov 05 19:36:05 CET 2006 Stefan Farfeleder <stefanf@FreeBSD.org> When parsing an invalid parameter expansion (eg. ${} or ${foo@bar}) do not
issue a syntax error immediately but save the information that it is erroneous
for later when the parameter expansion is actually done. This means eg. "false
&& ${}" will not generate an error which seems to be required by POSIX.
Include the invalid parameter expansion in the error message (sometimes
abbreviated with ... because recovering it would require a lot of code).
PR: 105078
Submitted by: emaste
diff 62addaefc90626acb3e1950378964fe08c2c3ef5 Sun Nov 05 19:36:05 CET 2006 Stefan Farfeleder <stefanf@FreeBSD.org> When parsing an invalid parameter expansion (eg. ${} or ${foo@bar}) do not
issue a syntax error immediately but save the information that it is erroneous
for later when the parameter expansion is actually done. This means eg. "false
&& ${}" will not generate an error which seems to be required by POSIX.
Include the invalid parameter expansion in the error message (sometimes
abbreviated with ... because recovering it would require a lot of code).
PR: 105078
Submitted by: emaste
|
| H A D | expand.c | diff 62addaefc90626acb3e1950378964fe08c2c3ef5 Sun Nov 05 19:36:05 CET 2006 Stefan Farfeleder <stefanf@FreeBSD.org> When parsing an invalid parameter expansion (eg. ${} or ${foo@bar}) do not
issue a syntax error immediately but save the information that it is erroneous
for later when the parameter expansion is actually done. This means eg. "false
&& ${}" will not generate an error which seems to be required by POSIX.
Include the invalid parameter expansion in the error message (sometimes
abbreviated with ... because recovering it would require a lot of code).
PR: 105078
Submitted by: emaste
diff 62addaefc90626acb3e1950378964fe08c2c3ef5 Sun Nov 05 19:36:05 CET 2006 Stefan Farfeleder <stefanf@FreeBSD.org> When parsing an invalid parameter expansion (eg. ${} or ${foo@bar}) do not
issue a syntax error immediately but save the information that it is erroneous
for later when the parameter expansion is actually done. This means eg. "false
&& ${}" will not generate an error which seems to be required by POSIX.
Include the invalid parameter expansion in the error message (sometimes
abbreviated with ... because recovering it would require a lot of code).
PR: 105078
Submitted by: emaste
|
| H A D | parser.c | diff 62addaefc90626acb3e1950378964fe08c2c3ef5 Sun Nov 05 19:36:05 CET 2006 Stefan Farfeleder <stefanf@FreeBSD.org> When parsing an invalid parameter expansion (eg. ${} or ${foo@bar}) do not
issue a syntax error immediately but save the information that it is erroneous
for later when the parameter expansion is actually done. This means eg. "false
&& ${}" will not generate an error which seems to be required by POSIX.
Include the invalid parameter expansion in the error message (sometimes
abbreviated with ... because recovering it would require a lot of code).
PR: 105078
Submitted by: emaste
diff 62addaefc90626acb3e1950378964fe08c2c3ef5 Sun Nov 05 19:36:05 CET 2006 Stefan Farfeleder <stefanf@FreeBSD.org> When parsing an invalid parameter expansion (eg. ${} or ${foo@bar}) do not
issue a syntax error immediately but save the information that it is erroneous
for later when the parameter expansion is actually done. This means eg. "false
&& ${}" will not generate an error which seems to be required by POSIX.
Include the invalid parameter expansion in the error message (sometimes
abbreviated with ... because recovering it would require a lot of code).
PR: 105078
Submitted by: emaste
|