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-19 16:33 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... ======================================================================
---------------------------------------------------------------------- (0006550) kre (reporter) - 2023-10-19 16:33 https://www.austingroupbugs.net/view.php?id=1778#c6550 ---------------------------------------------------------------------- Re https://www.austingroupbugs.net/view.php?id=1778#c6548 I mentioned earlier (not sure which note it was) that a change to an env var which is being overridden by a higher priority one would be OK, but to specify just that the language would have to be much more specific than your last attempt, rather than "would change the current locale" it would need to say something more like "is guaranteed to be unable to alter the current locale" (and you could add that example somewhere in the application usage showing one example of how to make that guarantee if that would be useful). WRT: My concern is that there might be scripts in existence [...] When making something unspecified here (as distinct from when deciding to specify some particular behaviour) this isn't an issue we need to worry about at all. Explicitly making something unspecified is our way of telling implementers that they do not need to change whatever they currently do. If a script writer wants a script that will work on any POSIX compat shell, they need to worry about this, but if someone has a script that is currently working in the environment in which they use it, that they are using unspecified behaviour is irrelevant - it works, there's no reason (from here) for the implementation they're using to alter, so it will just keep on working. But now, if they were to try to move the script to a different environment, where things currently (and will continue to) work differently, we would be avoiding arguments between users and implementations about "your shell is broken because my script works fine with this other shell" since the "your shell" maintainers can simply point to the standard to show that the script is using something not guaranteed to work. Note that the alternative to all of this concern about particular vars being unspecified to use with read would have been to simply specify late binding of the vars. All field splitting first, then all assignments after that, as I did in my original suggestion. But that one would have required some implementations to alter in to remain conformant, and that might have broken some scripts (as unlikely as it seems, as there are really just these few variables where it makes any difference) in which case your concern would have been valid. So I'd still suggest opting for maximum simplicity here, along with maximum clarity, and minimum conditional "unspecified unless" type complexity. There really is no harm to that. 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 2023-10-03 13:42 geoffclare Note Added: 0006512 2023-10-04 14:42 kre Note Added: 0006513 2023-10-04 17:36 kre Note Added: 0006514 2023-10-05 08:59 geoffclare Note Added: 0006515 2023-10-05 11:08 kre Note Added: 0006516 2023-10-05 14:53 geoffclare Note Added: 0006517 2023-10-05 15:34 kre Note Edited: 0006516 2023-10-05 15:35 kre Note Edited: 0006516 2023-10-05 15:36 kre Note Edited: 0006516 2023-10-05 15:38 kre Note Added: 0006519 2023-10-05 15:41 kre Note Edited: 0006513 2023-10-06 07:58 geoffclare Note Edited: 0006515 2023-10-06 21:41 chet_ramey Note Added: 0006524 2023-10-10 11:06 geoffclare Note Edited: 0006515 2023-10-10 14:36 geoffclare Note Added: 0006526 2023-10-10 17:19 kre Note Added: 0006527 2023-10-11 08:04 geoffclare Note Added: 0006528 2023-10-11 17:13 kre Note Added: 0006529 2023-10-12 08:30 geoffclare Note Added: 0006530 2023-10-12 18:33 kre Note Added: 0006531 2023-10-12 18:45 kre Note Edited: 0006516 2023-10-12 18:54 kre Note Added: 0006532 2023-10-16 09:02 geoffclare Note Added: 0006533 2023-10-16 09:03 geoffclare Note Edited: 0006533 2023-10-16 09:19 geoffclare Note Added: 0006534 2023-10-16 21:43 kre Note Added: 0006537 2023-10-16 22:10 kre Note Added: 0006538 2023-10-17 13:34 geoffclare Note Added: 0006543 2023-10-18 00:08 kre Note Added: 0006547 2023-10-19 14:05 geoffclare Note Added: 0006548 2023-10-19 16:33 kre Note Added: 0006550 ======================================================================
