[1003.1(2016/18)/Issue7+TC2 0001446]: Does a shall-fail in terms of an undefined limits.h macro impose any requirement?

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1446 
== 
Reported By:dalias
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1446
Category:   System Interfaces
Type:   Clarification Requested
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Rich Felker 
Organization:   musl libc 
User Reference:  
Section:posix_spawn_file_actions_addopen et al 
Page Number:unknown 
Line Number:unknown 
Interp Status:  --- 
Final Accepted Text:See
https://austingroupbugs.net/view.php?id=1446#c5511 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2021-01-25 18:17 UTC
Last Modified:  2021-11-25 16:28 UTC
== 
Summary:Does a shall-fail in terms of an undefined limits.h
macro impose any requirement?
== 

-- 
 (0005539) geoffclare (manager) - 2021-11-25 16:28
 https://austingroupbugs.net/view.php?id=1446#c5539 
-- 
The troff changes have been applied in gitlab. The frontmatter change has
been applied in an updated version to be used for Issue 8 draft 3. In the
unlikely event that we do an Issue 7 TC3, the frontmatter change will also
be needed there. 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-01-25 18:17 dalias New Issue
2021-01-25 18:17 dalias Name  => Rich Felker 
2021-01-25 18:17 dalias Organization  => musl libc   
2021-01-25 18:17 dalias Section   =>
posix_spawn_file_actions_addopen et al
2021-01-25 18:17 dalias Page Number   => unknown 
2021-01-25 18:17 dalias Line Number   => unknown 
2021-01-26 09:39 geoffclare Note Added: 0005209  
2021-01-26 17:27 dalias Note Added: 0005211  
2021-01-26 18:05 shware_systems Note Added: 0005212  
2021-01-26 18:15 dalias Note Added: 0005213  
2021-01-26 18:49 shware_systems Note Added: 0005214  
2021-10-28 16:35 nick   Note Added: 0005511  
2021-10-28 16:36 nick   Note Edited: 0005511 
2021-10-28 16:37 nick   Note Edited: 0005511 
2021-10-28 16:38 nick   Interp Status => --- 
2021-10-28 16:38 nick   Final Accepted Text   => See
https://austingroupbugs.net/view.php?id=1446#c5511
2021-10-28 16:38 nick   Status   New => Resolved 
2021-10-28 16:38 nick   Resolution   Open => Accepted As
Marked
2021-10-28 16:39 nick   Tag Attached: tc3-2008   
2021-10-28 16:39 nick   Note Edited: 0005511 
2021-11-25 16:28 geoffclare Note Added: 0005539  
2021-11-25 16:28 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001449]: "Decimal-point character" vs. "radix character"

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1449 
== 
Reported By:rhansen
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1449
Category:   Base Definitions and Headers
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Richard Hansen 
Organization:
User Reference:  
Section:3 Definitions 
Page Number: 
Line Number: 
Interp Status:  --- 
Final Accepted Text: 
Resolution: Accepted
Fixed in Version:   
== 
Date Submitted: 2021-02-04 17:25 UTC
Last Modified:  2021-11-25 16:17 UTC
== 
Summary:"Decimal-point character" vs. "radix character"
==
Relationships   ID  Summary
--
has duplicate   0001450 The term decimal-point character is fre...
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-02-04 17:25 rhansenNew Issue
2021-02-04 17:25 rhansenName  => Richard Hansen  
2021-02-04 17:25 rhansenSection   => 3 Definitions   
2021-02-04 17:25 rhansenInterp Status => --- 
2021-02-04 17:25 rhansenDesired Action Updated   
2021-02-04 17:27 rhansenDescription Updated  
2021-02-04 19:44 Don Cragun Relationship added   has duplicate 0001450
2021-11-04 16:19 Don Cragun Status   New => Resolved 
2021-11-04 16:19 Don Cragun Resolution   Open => Accepted
2021-11-04 16:20 Don Cragun Tag Attached: tc3-2008   
2021-11-25 16:17 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001444]: Broken cross-references to wordexp()

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1444 
== 
Reported By:geoffclare
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1444
Category:   Base Definitions and Headers
Type:   Error
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Geoff Clare 
Organization:   The Open Group 
User Reference:  
Section: 
Page Number:466 
Line Number:16113 
Interp Status:  --- 
Final Accepted Text: 
Resolution: Accepted
Fixed in Version:   
== 
Date Submitted: 2021-01-19 10:42 UTC
Last Modified:  2021-11-25 16:12 UTC
== 
Summary:Broken cross-references to wordexp()
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-01-19 10:42 geoffclare New Issue
2021-01-19 10:42 geoffclare Name  => Geoff Clare 
2021-01-19 10:42 geoffclare Organization  => The Open Group  
2021-01-19 10:42 geoffclare Section   =>  
2021-01-19 10:42 geoffclare Page Number   => 466 
2021-01-19 10:42 geoffclare Line Number   => 16113   
2021-01-19 10:42 geoffclare Interp Status => --- 
2021-10-28 15:52 Don Cragun Tag Attached: tc3-2008   
2021-10-28 15:53 Don Cragun Status   New => Resolved 
2021-10-28 15:53 Don Cragun Resolution   Open => Accepted
2021-11-25 16:12 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001443]: Definition of "pattern" omits some uses

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1443 
== 
Reported By:geoffclare
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1443
Category:   Base Definitions and Headers
Type:   Omission
Severity:   Objection
Priority:   normal
Status: Applied
Name:   Geoff Clare 
Organization:   The Open Group 
User Reference:  
Section:3.274 Pattern 
Page Number:77 
Line Number:2224 
Interp Status:  --- 
Final Accepted Text: 
Resolution: Accepted
Fixed in Version:   
== 
Date Submitted: 2021-01-19 10:40 UTC
Last Modified:  2021-11-25 16:10 UTC
== 
Summary:Definition of "pattern" omits some uses
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-01-19 10:40 geoffclare New Issue
2021-01-19 10:40 geoffclare Name  => Geoff Clare 
2021-01-19 10:40 geoffclare Organization  => The Open Group  
2021-01-19 10:40 geoffclare Section   => 3.274 Pattern   
2021-01-19 10:40 geoffclare Page Number   => 77  
2021-01-19 10:40 geoffclare Line Number   => 2224
2021-01-19 10:40 geoffclare Interp Status => --- 
2021-10-28 15:50 Don Cragun Status   New => Resolved 
2021-10-28 15:50 Don Cragun Resolution   Open => Accepted
2021-10-28 15:51 nick   Tag Attached: tc3-2008   
2021-11-25 16:10 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001442]: Improvement to getopts example, remove double negation

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1442 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1442
Category:   Shell and Utilities
Type:   Enhancement Request
Severity:   Comment
Priority:   normal
Status: Applied
Name:   Andras Farkas 
Organization:
User Reference:  
Section:getopts 
Page Number:2840 
Line Number:93538 and 93541 
Interp Status:  --- 
Final Accepted Text: 
Resolution: Accepted
Fixed in Version:   
== 
Date Submitted: 2021-01-10 13:10 UTC
Last Modified:  2021-11-25 16:08 UTC
== 
Summary:Improvement to getopts example, remove double
negation
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-01-10 13:10 andras_farkas  New Issue
2021-01-10 13:10 andras_farkas  Name  => Andras Farkas   
2021-01-10 13:10 andras_farkas  Section   => getopts 
2021-01-10 22:42 Don Cragun Page Number   => 2840
2021-01-10 22:42 Don Cragun Line Number   => 93538 and 93541 
2021-01-10 22:42 Don Cragun Interp Status => --- 
2021-10-28 15:48 Don Cragun Status   New => Resolved 
2021-10-28 15:48 Don Cragun Resolution   Open => Accepted
2021-10-28 15:48 Don Cragun Tag Attached: tc3-2008   
2021-11-25 16:08 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001441]: PS4 should be printed for non-interactive shells as well

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1441 
== 
Reported By:rhansen
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1441
Category:   Shell and Utilities
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Richard Hansen 
Organization:
User Reference:  
Section:2.5.3 Shell Variables, PS4 
Page Number:2352 
Line Number:74965 
Interp Status:  --- 
Final Accepted Text: 
Resolution: Accepted
Fixed in Version:   
== 
Date Submitted: 2021-01-07 16:56 UTC
Last Modified:  2021-11-25 16:07 UTC
== 
Summary:PS4 should be printed for non-interactive shells as
well
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-01-07 16:56 rhansenNew Issue
2021-01-07 16:56 rhansenName  => Richard Hansen  
2021-01-07 16:56 rhansenSection   => 2.5.3 Shell
Variables, PS4
2021-01-07 16:56 rhansenPage Number   => 2352
2021-01-07 16:56 rhansenLine Number   => 74965   
2021-01-07 16:56 rhansenInterp Status => --- 
2021-10-28 15:44 Don Cragun Status   New => Resolved 
2021-10-28 15:44 Don Cragun Resolution   Open => Accepted
2021-10-28 15:44 Don Cragun Tag Attached: tc3-2008   
2021-11-25 16:07 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001438]: iconv: clarify which "codeset" is meant

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has a resolution that has been APPLIED. 
== 
https://austingroupbugs.net/view.php?id=1438 
== 
Reported By:steffen
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1438
Category:   System Interfaces
Type:   Clarification Requested
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   steffen 
Organization:
User Reference:  
Section:iconv 
Page Number:1123 
Line Number:38001 
Interp Status:  --- 
Final Accepted Text: 
Resolution: Accepted
Fixed in Version:   
== 
Date Submitted: 2020-12-17 19:19 UTC
Last Modified:  2021-11-25 16:05 UTC
== 
Summary:iconv: clarify which "codeset" is meant
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2020-12-17 19:19 steffenNew Issue
2020-12-17 19:19 steffenName  => steffen 
2020-12-17 19:19 steffenSection   => iconv   
2020-12-17 19:19 steffenPage Number   => 1123
2020-12-17 19:19 steffenLine Number   => 38001   
2021-10-14 15:38 geoffclare Interp Status => --- 
2021-10-14 15:38 geoffclare Status   New => Resolved 
2021-10-14 15:38 geoffclare Resolution   Open => Accepted
2021-10-14 15:38 geoffclare Tag Attached: tc3-2008   
2021-11-25 16:05 geoffclare Status   Resolved => Applied 
==

[1003.1(2016/18)/Issue7+TC2 0001488]: pwd RATIONALE does not account for ENOSPC

[Austin Group Bug Tracker via austin-group-l at The Open Group]

A NOTE has been added to this issue. 
== 
https://austingroupbugs.net/view.php?id=1488 
== 
Reported By:geoffclare
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1488
Category:   Shell and Utilities
Type:   Error
Severity:   Comment
Priority:   normal
Status: Under Review
Name:   Geoff Clare 
Organization:   The Open Group 
User Reference:  
Section:pwd 
Page Number:3131 
Line Number:104830 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2021-07-12 09:31 UTC
Last Modified:  2021-11-25 14:47 UTC
== 
Summary:pwd RATIONALE does not account for ENOSPC
== 

-- 
 (0005538) geoffclare (manager) - 2021-11-25 14:47
 https://austingroupbugs.net/view.php?id=1488#c5538 
-- 
On page 3131 line 104819 section pwd, change:If an error is
detected, output shall not be written to standard output, a diagnostic
message shall be written to standard error, and the exit status is not
zero.to:If an error is detected other than a write
error when writing to standard output, no output shall be written to
standard output, a diagnostic message shall be written to standard error,
and the exit status shall be non-zero.
On page 3131 line 104830 section pwd, change:In most utilities,
if an error occurs, partial output may be written to standard output. This
does not happen in historical implementations of pwd. Because
pwd is frequently used in historical shell scripts without checking
the exit status, it is important that the historical behavior is required
here; therefore, the CONSEQUENCES OF ERRORS section specifically disallows
any partial output being written to standard
output.to:In most utilities, if an error occurs,
partial output may be written to standard output. This does not happen in
historical implementations of pwd (unless an error condition causes
a partial write). Because pwd is frequently used in historical shell
scripts without checking the exit status, it is important that the
historical behavior is required here; therefore, the CONSEQUENCES OF ERRORS
section specifically disallows any partial output being written to standard
output, except when a write error occurs when writing to standard
output. 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-07-12 09:31 geoffclare New Issue
2021-07-12 09:31 geoffclare Name  => Geoff Clare 
2021-07-12 09:31 geoffclare Organization  => The Open Group  
2021-07-12 09:31 geoffclare Section   => pwd 
2021-07-12 09:31 geoffclare Page Number   => 3131
2021-07-12 09:31 geoffclare Line Number   => 104830  
2021-07-12 09:31 geoffclare Interp Status => --- 
2021-11-18 17:16 Don Cragun Status   New => Resolved 
2021-11-18 17:16 Don Cragun Resolution   Open => Accepted
2021-11-18 17:17 Don Cragun Tag Attached: tc3-2008   
2021-11-25 14:45 geoffclare Note Added: 0005537  
2021-11-25 14:45 geoffclare Status   Resolved => Under
Review
2021-11-25 14:45 geoffclare Resolution   Accepted => Reopened
2021-11-25 14:47 geoffclare Note Added: 0005538  
==

[1003.1(2016/18)/Issue7+TC2 0001488]: pwd RATIONALE does not account for ENOSPC

[Austin Group Bug Tracker via austin-group-l at The Open Group]

The following issue has been REOPENED. 
== 
https://austingroupbugs.net/view.php?id=1488 
== 
Reported By:geoffclare
Assigned To:
== 
Project:1003.1(2016/18)/Issue7+TC2
Issue ID:   1488
Category:   Shell and Utilities
Type:   Error
Severity:   Comment
Priority:   normal
Status: Under Review
Name:   Geoff Clare 
Organization:   The Open Group 
User Reference:  
Section:pwd 
Page Number:3131 
Line Number:104830 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2021-07-12 09:31 UTC
Last Modified:  2021-11-25 14:45 UTC
== 
Summary:pwd RATIONALE does not account for ENOSPC
== 

-- 
 (0005537) geoffclare (manager) - 2021-11-25 14:45
 https://austingroupbugs.net/view.php?id=1488#c5537 
-- 
Reopening, as it was pointed out on the mailing list that the text should
not single out ENOSPC; there are other error conditions that can cause a
partial write. New proposed text will follow. 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2021-07-12 09:31 geoffclare New Issue
2021-07-12 09:31 geoffclare Name  => Geoff Clare 
2021-07-12 09:31 geoffclare Organization  => The Open Group  
2021-07-12 09:31 geoffclare Section   => pwd 
2021-07-12 09:31 geoffclare Page Number   => 3131
2021-07-12 09:31 geoffclare Line Number   => 104830  
2021-07-12 09:31 geoffclare Interp Status => --- 
2021-11-18 17:16 Don Cragun Status   New => Resolved 
2021-11-18 17:16 Don Cragun Resolution   Open => Accepted
2021-11-18 17:17 Don Cragun Tag Attached: tc3-2008   
2021-11-25 14:45 geoffclare Note Added: 0005537  
2021-11-25 14:45 geoffclare Status   Resolved => Under
Review
2021-11-25 14:45 geoffclare Resolution   Accepted => Reopened
==

Re: pwd and CONSEQUENCES OF ERRORS

[Geoff Clare via austin-group-l at The Open Group]

Vincent Lefevre wrote, on 25 Nov 2021:
>
> https://austingroupbugs.net/view.php?id=1488 about pwd and
> CONSEQUENCES OF ERRORS considers ENOSPC only.
> 
> But are there other errors that may yield a partial write?
> I'm thinking of EFBIG and EPIPE, in particular.

Good point.  The discussion that spawned bug 1488 had centred around
ENOSPC, so I suppose that's why I singled it out in my proposed
changes.  There are certainly other ways to get a partial write.
The write() page says:

If a write() requests that more bytes be written than there is
room for (for example, the file size limit of the process or the
physical end of a medium), only as many bytes as there is room for
shall be written.

I think the simplest solution would be for bug 1488 resolution to
say "an error condition" instead of "an [ENOSPC] condition".

I will reopen it and put in a new proposed resolution.

-- 
Geoff Clare 
The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England

pwd and CONSEQUENCES OF ERRORS

[Vincent Lefevre via austin-group-l at The Open Group]

https://austingroupbugs.net/view.php?id=1488 about pwd and
CONSEQUENCES OF ERRORS considers ENOSPC only.

But are there other errors that may yield a partial write?
I'm thinking of EFBIG and EPIPE, in particular.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)