A NOTE has been added to this issue. ====================================================================== https://www.austingroupbugs.net/view.php?id=1778 ====================================================================== Reported By: kre Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1778 Category: Shell and Utilities Type: Enhancement Request Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section: XCU 3/read Page Number: 3291-3294 Line Number: 111869-111878, 111961-111963, 11946, 11979-11980 Final Accepted Text: ====================================================================== Date Submitted: 2023-10-02 13:58 UTC Last Modified: 2023-10-03 12:11 UTC ====================================================================== Summary: The read utility needs field splitting updates/corrections )and a little more) ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001649 Field splitting is woefully under speci... ======================================================================
---------------------------------------------------------------------- (0006511) kre (reporter) - 2023-10-03 12:11 https://www.austingroupbugs.net/view.php?id=1778#c6511 ---------------------------------------------------------------------- Further re https://www.austingroupbugs.net/view.php?id=1778#c6509 I assumed in https://www.austingroupbugs.net/view.php?id=1778#c6510 that your "already clearly states" meant what is in Draft 3 (and earlier) already, rather than what is in my proposed (but needs wordsmithing) text in https://www.austingroupbugs.net/view.php?id=1778#c6500 In the latter I do specify left to right (or first to last) assignment of the variables to which data is to be applied - as that's what shells do, so it seemed reasonable - but there is a potential problem for the duplicate var name case, it also says: Any variables to which no value has yet been assigned shall be assigned an empty string. which would imply that the empty string assignments happen after the others, but (even though I wrote that) is unclear as to what "variables to which no value has yet been assigned" means in the case we have read a b a <<\! x y ! clearly a=x and b=y happens, but now are we supposed to also do a='' for the duplicate use of a (as that's what shells do) or is a in that case a variable to which a value has already been assigned. This kind of thing needs to be bulletproof. Issue History Date Modified Username Field Change ====================================================================== 2023-10-02 13:58 kre New Issue 2023-10-02 13:58 kre Name => Robert Elz 2023-10-02 13:58 kre Section => XCU 3/read 2023-10-02 13:58 kre Page Number => 3291-3294 2023-10-02 13:58 kre Line Number => 111869-111878, 111961-111963, 11946, 11979-11980 2023-10-02 14:00 kre Note Added: 0006500 2023-10-02 14:02 kre Note Edited: 0006500 2023-10-02 14:20 kre Note Added: 0006502 2023-10-02 14:22 kre Note Edited: 0006502 2023-10-02 14:24 kre Note Edited: 0006502 2023-10-02 14:30 kre Note Added: 0006503 2023-10-02 14:33 kre Note Edited: 0006502 2023-10-02 14:34 kre Note Edited: 0006502 2023-10-02 14:44 kre Note Edited: 0006500 2023-10-02 16:18 geoffclare Project 1003.1(2013)/Issue7+TC1 => Issue 8 drafts 2023-10-02 16:19 geoffclare version => Draft 3 2023-10-02 16:20 geoffclare Note Added: 0006507 2023-10-02 16:21 geoffclare Relationship added related to 0001649 2023-10-03 09:23 geoffclare Note Added: 0006509 2023-10-03 11:59 kre Note Added: 0006510 2023-10-03 12:11 kre Note Added: 0006511 ======================================================================
