Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
0000914 |
[1003.1(2013)/Issue7+TC1] Shell and Utilities |
Editorial |
Enhancement Request |
2015-01-22 18:04 |
2024-06-11 09:02 |
|
Reporter |
rhansen |
View Status |
public |
|
Assigned To |
|
Priority |
normal |
Resolution |
Accepted |
|
Status |
Closed |
|
|
|
|
Name |
Richard Hansen |
Organization |
BBN |
User Reference |
|
Section |
2.8.1 Consequences of Shell Errors table |
Page Number |
2337 |
Line Number |
74293-74294 (approximately) |
Interp Status |
--- |
Final Accepted Text |
|
|
Summary |
0000914: redirection error with function invocations or compound commands should not cause the shell to exit |
Description |
The changes made for 0000882 specify that redirection errors with function executions and compound commands may cause the shell to exit. While discussing 0000882 during the 2015-01-22 teleconference, consensus was that the implementations that are known to exit in these cases (Bourne shell and ksh88 and its derivatives) are believed to be buggy and should not exit.
The "may exit" should be changed to "shall not exit". (We wanted to make this change along with 0000882, but this change must be made in Issue 8, not Issue 7 TC2.) |
Desired Action |
After applying 0000882, on page 2337 lines 74293-74294 (XCU 2.8.1 Consequences of Shell Errors table), change:Redirection error with compound commands | may exit(3) | shall not exit | yes
Redirection error with function execution | may exit(3) | shall not exit | yes to:Redirection error with compound commands | shall not exit | shall not exit | yes
Redirection error with function execution | shall not exit | shall not exit | yes On page 2337 delete the new Note (3):(3) A future version of this standard may require the shell to not exit in this condition. |
Tags |
issue8 |
|
Attached Files |
|
|