A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1806 ====================================================================== Reported By: calestyo Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1806 Category: Shell and Utilities Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: Christoph Anton Mitterer Organization: User Reference: Section: Shell Command Language Page Number: 2571 Line Number: 83916, ff. Final Accepted Text: ====================================================================== Date Submitted: 2024-02-02 22:53 UTC Last Modified: 2024-03-25 16:29 UTC ====================================================================== Summary: ambiguous description of which attribtes `unset` unsets in case of readonly attribute being set ======================================================================
---------------------------------------------------------------------- (0006727) geoffclare (manager) - 2024-03-25 16:29 https://austingroupbugs.net/view.php?id=1806#c6727 ---------------------------------------------------------------------- Proposed interpretation (review timer to start after approval of issue 8) ... Interpretation response ------------------------ The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: ------------- The standard should not attempt to specify behavior for non-standard variable attributes. An application which sets such an attribute is using an extension, and the behavior of the extension is entirely a matter for the implementation. Notes to the Editor (not part of this interpretation): ------------------------------------------------------- On page 2571 line 83916-83923, replace the first four paragraphs of DESCRIPTION with: <blockquote>The <i>unset</i> utility shall unset a variable or function definition specified by each <i>name</> operand, as follows:<ul> <li>If <b>−v</b> is specified, <i>name</i> refers to a variable. If the named variable exists and does not have the <i>readonly</i> attribute, the shell shall unset it and shall remove the <i>export</i> attribute if the variable has it. Read-only variables cannot be unset.</li> <li>If <b>−f</b> is specified, <i>name</i> refers to a function. If the named function exists, the shell shall unset the function definition.</li> <li>If neither <b>−f</b> nor <b>−v</b> is specified and <i>name</i> refers to a variable that exists, the variable shall be unset as if <b>-v</b> was specified; if a variable by that name does not exist, it is unspecified whether a function by that name, if any, is unset.</li></ul></blockquote> On page 2573 line 83953, change: <blockquote>All <i>name</i> operands were successfully unset.</blockquote> to: <blockquote>Each <i>name</i> operand either did not exist or was successfully unset.</blockquote> Issue History Date Modified Username Field Change ====================================================================== 2024-02-02 22:53 calestyo New Issue 2024-02-02 22:53 calestyo Name => Christoph Anton Mitterer 2024-02-02 22:53 calestyo Section => Shell Command Language 2024-02-02 22:53 calestyo Page Number => 2571 2024-02-02 22:53 calestyo Line Number => 83916, ff. 2024-02-03 00:30 larryv Note Added: 0006647 2024-02-13 20:10 mirabilos Note Added: 0006653 2024-02-13 20:25 mirabilos Note Added: 0006654 2024-02-13 22:48 calestyo Note Added: 0006655 2024-02-13 22:55 calestyo Note Added: 0006656 2024-02-25 07:34 kre Note Added: 0006679 2024-02-25 21:50 calestyo Note Added: 0006680 2024-02-25 22:36 larryv Note Added: 0006681 2024-02-25 23:00 calestyo Note Added: 0006682 2024-02-25 23:16 larryv Note Added: 0006683 2024-02-25 23:22 larryv Note Added: 0006684 2024-03-25 16:29 geoffclare Note Added: 0006727 ======================================================================
