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:                     Resolved
Name:                       Robert Elz 
Organization:                
User Reference:              
Section:                    XCU 3 / getopts 
Page Number:                2955 - 2959 
Line Number:                98803  - 98966 
Final Accepted Text:        See
https://austingroupbugs.net/view.php?id=1784#c6600. 
Resolution:                 Accepted As Marked
Fixed in Version:           
====================================================================== 
Date Submitted:             2023-10-22 06:14 UTC
Last Modified:              2023-12-14 09:46 UTC
====================================================================== 
Summary:                    getopts specification needs fixing (multiple issues)
====================================================================== 

---------------------------------------------------------------------- 
 (0006608) geoffclare (manager) - 2023-12-14 09:46
 https://austingroupbugs.net/view.php?id=1784#c6608 
---------------------------------------------------------------------- 
Re https://austingroupbugs.net/view.php?id=1784#c6606 It is not a fabrication,
it is a factually correct
statement about the decision-making process during resolution of bug
https://austingroupbugs.net/view.php?id=191. The decision we made was to require
the requested leading
<plus-sign> behaviour for getopt() but intentionally leave it unspecified
for getopts in order to allow it to be used for extensions, as stated in
the rationale for getopt():<blockquote>Note that the use of a leading
<plus-sign> in <i>optstring</i> is only standardized for <i>getopt</i>().
Use of a  <plus-sign> is intentionally left unspecified for the
<i>getopts</i> utility, where historical implementations did not require a
leading <plus-sign> for conforming behavior, and because  some historical
<i>getopts</i> implementations used a leading <plus-sign> for a different
extension.</blockquote> 

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                          
2023-10-28 06:25 Don Cragun     Note Added: 0006558                          
2023-10-28 06:27 Don Cragun     Relationship deleted     related to 0001535  
2023-10-28 06:28 Don Cragun     Relationship deleted     related to 0001393  
2023-10-28 06:34 Don Cragun     Relationship deleted     parent of 0000351   
2023-10-28 06:34 kre            Note Edited: 0006556                         
2023-11-13 18:09 shware_systems Note Added: 0006568                          
2023-11-13 20:16 kre            Note Added: 0006569                          
2023-11-14 09:44 geoffclare     Tag Detached: issue8                         
2023-11-15 22:23 salewski       Issue Monitored: salewski                    
2023-12-11 17:37 geoffclare     Note Added: 0006598                          
2023-12-11 17:41 Don Cragun     Note Added: 0006599                          
2023-12-11 17:50 Don Cragun     Note Added: 0006600                          
2023-12-11 17:55 Don Cragun     Note Edited: 0006600                         
2023-12-11 17:58 Don Cragun     Note Edited: 0006600                         
2023-12-11 17:59 Don Cragun     Status                   New => Resolved     
2023-12-11 17:59 Don Cragun     Resolution               Open => Accepted As
Marked
2023-12-11 18:01 Don Cragun     Final Accepted Text       => See
https://austingroupbugs.net/view.php?id=1784#c6600.
2023-12-11 18:02 Don Cragun     Tag Attached: issue8                         
2023-12-11 19:22 Don Cragun     Note Deleted: 0006599                        
2023-12-11 23:41 kre            Note Added: 0006602                          
2023-12-11 23:42 kre            Note Edited: 0006602                         
2023-12-11 23:52 kre            Note Added: 0006603                          
2023-12-12 09:25 geoffclare     Note Added: 0006604                          
2023-12-12 09:25 geoffclare     Note Edited: 0006604                         
2023-12-12 21:22 kre            Note Added: 0006606                          
2023-12-14 07:05 Don Cragun     Note Added: 0006607                          
2023-12-14 09:46 geoffclare     Note Added: 0006608                          
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to