Anonymous | Login | 2024-04-19 23:29 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0000443 | [2008-TC1] Shell and Utilities | Objection | Omission | 2011-05-14 17:40 | 2011-05-19 16:26 | ||
Reporter | jilles | View Status | public | ||||
Assigned To | ajosey | ||||||
Priority | normal | Resolution | Rejected | ||||
Status | Closed | Product Version | Draft 1 | ||||
Name | Jilles Tjoelker | ||||||
Organization | |||||||
User Reference | |||||||
Section | 2.8.1 Consequences of Shell Errors, 2.14 dot, 2.14 eval | ||||||
Page Number | 2315,2341,2343 | ||||||
Line Number | 73050-73051,74053,74110 | ||||||
Interp Status | --- | ||||||
Final Accepted Text | |||||||
Summary | 0000443: poor wording about errors in interactive shells | ||||||
Description |
Various pieces of text suggest that interactive shells continue executing a command after errors (albeit with $? != 0) that would cause a non-interactive shell to exit. This does not seem very useful and does not match most implementations. Most implementations abort the commands currently in progress, set $? to a value greater than 0 and return to the prompt. Change Number XCU/TC1/D1/0023 [114] makes this worse, suggesting that an interactive shell continue executing after an error in dot. For example, I would expect the following to print an error message, and no "continued" message: $ . /nonexistent; echo continued $? Change Number: XCU/TC1/D1/0025 [114] makes this worse, suggesting that an interactive shell continue executing after an error in eval. My assumption is that if something is mentioned explicitly in the "Exit status" subsection of a description of a special built-in utility in 2.14, this means that the shell continues executing commands after the special builtin; in other words, "shall exit" errors from 2.8.1 are not mentioned there. |
||||||
Desired Action |
In 2.8.1 Consequences of Shell Errors, change In all of the cases shown in the table, an interactive shell shall write a diagnostic message to standard error without exiting. to If any of the errors shown as ‘‘shall exit’’ or ‘‘(may) exit’’ occur in an interactive shell, the shell shall write a diagnostic message to standard error, set $? to a value greater than 0 and return to the prompt. In 2.14 dot, do not apply XCU/TC1/D1/0023 [114]. If the section is not clear enough, it may be necessary to clarify that if the dot script cannot be found or opened it is a "Dot script not found" error per 2.8.1 and if the commands cannot be parsed it is a "Shell language syntax error" per 2.8.1. In 2.14 eval, do not apply XCU/TC1/D1/0025 [114]. |
||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
Relationships | |||||||
|
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |