A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1784 ====================================================================== Reported By: kre Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1784 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section: XCU 3 / getopts Page Number: 2955 - 2959 Line Number: 98803 - 98966 Final Accepted Text: ====================================================================== Date Submitted: 2023-10-22 06:14 UTC Last Modified: 2023-10-28 05:36 UTC ====================================================================== Summary: getopts specification needs fixing (multiple issues) ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001535 Poor description of declaration (all re... related to 0001393 'command' should not be treated as a de... parent of 0000351 certain shell special built-ins should ... ======================================================================
---------------------------------------------------------------------- (0006556) kre (reporter) - 2023-10-28 05:36 https://austingroupbugs.net/view.php?id=1784#c6556 ---------------------------------------------------------------------- How did this bug manage to get related to https://austingroupbugs.net/view.php?id=351 https://austingroupbugs.net/view.php?id=1393 and https://austingroupbugs.net/view.php?id=1535 ? Those are all related to declaration utilities (export, readonly ...) and I don't see how anything related to that issue impacts upon getopts at all. What's the supposed relationship? getopts is certainly not a declaration utility, if it happens to have any args of the form "var=value" (not all that likely, as use of the arg...) optional arg list seems very rare to me, not sure I have ever seen that done, and that would be the only place an arg like this could occur), then I think it would be totally inappropriate for such an arg to have any special parsing rules applied to it. There is nothing in this bug that pertains to how getopts own args are parsed - it is all about how getopts processes them, and what it puts in OPTIND. [Aside: I know I gave an example in the bug description, where I used the optional arg... method to provide the args to be parsed - that was just to economise upon the bug report text, otherwise I would have needed an extra "set -- ..." command to set the positional params to the desired values first.] Issue History Date Modified Username Field Change ====================================================================== 2023-10-22 06:14 kre New Issue 2023-10-22 06:14 kre Name => Robert Elz 2023-10-22 06:14 kre Section => XCU 3 / getopts 2023-10-22 06:14 kre Page Number => 2955 - 2959 2023-10-22 06:14 kre Line Number => 98803 - 98966 2023-10-22 06:40 kre Tag Attached: issue8 2023-10-28 05:08 Don Cragun Relationship added related to 0001535 2023-10-28 05:10 Don Cragun Relationship added related to 0001393 2023-10-28 05:10 Don Cragun Relationship added parent of 0000351 2023-10-28 05:19 kre Note Added: 0006555 2023-10-28 05:36 kre Note Added: 0006556 ======================================================================
