A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1785 ====================================================================== Reported By: kre Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1785 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section: XCU 2.9.1.1 Page Number: 2483 Line Number: 80766-80778, 80790-80792 Final Accepted Text: ====================================================================== Date Submitted: 2023-10-28 04:09 UTC Last Modified: 2023-12-11 15:37 UTC ====================================================================== Summary: Conflict in specification of processing of declaration utilities ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001535 Poor description of declaration (all re... related to 0001393 'command' should not be treated as a de... related to 0000351 certain shell special built-ins should ... ======================================================================
---------------------------------------------------------------------- (0006597) geoffclare (manager) - 2023-12-11 15:37 https://austingroupbugs.net/view.php?id=1785#c6597 ---------------------------------------------------------------------- Suggested changes... On page 2483 line 80769 section 2.9.1.1, change:<blockquote>If there is a command name and it is recognized as a declaration utility, then any remaining words after the word that expanded to produce the command name, ...</blockquote>to:<blockquote>If there is a command name, the shell shall use one of the following methods to check whether the utility to be invoked is a declaration utility: <ul><li>The value, prior to expansion, of the word that expanded to produce the command name is matched lexically against the names of declaration utilities.</li> <li>The command name is matched lexically against the names of declaration utilities.</li></ul>If the chosen method identifies the utility to be invoked as a declaration utility, then any remaining words after the word that expanded to produce the command name, ...</blockquote> On page 2483 line 80778 section 2.9.1.1, change:<blockquote>For all other command names, words after the word that produced the command name shall be subject only to regular expansion.</blockquote>to:<blockquote>If the utility to be invoked is not identified as a declaration utility, words after the word that produced the command name shall be subject only to regular expansion.</blockquote> On page 2483 line 80790 section 2.9.1.1, delete:<blockquote>When determining whether a command name is a declaration utility, an implementation may use only lexical analysis. It is unspecified whether assignment context will be used if the command name would only become recognized as a declaration utility after word expansions.</blockquote> Issue History Date Modified Username Field Change ====================================================================== 2023-10-28 04:09 kre New Issue 2023-10-28 04:09 kre Name => Robert Elz 2023-10-28 04:09 kre Section => XCU 2.9.1.1 2023-10-28 04:09 kre Page Number => 2483 2023-10-28 04:09 kre Line Number => 80766-80778, 80790-80792 2023-10-28 05:48 kre Note Added: 0006557 2023-10-28 06:27 Don Cragun Relationship added related to 0001535 2023-10-28 06:28 Don Cragun Relationship added related to 0001393 2023-10-28 06:30 Don Cragun Relationship added related to 0000351 2023-10-30 14:07 chet_ramey Note Added: 0006559 2023-12-11 15:37 geoffclare Note Added: 0006597 ======================================================================
