View Issue Details

IDProjectCategoryView StatusLast Update
00017451003.1(2016/18)/Issue7+TC2Shell and Utilitiespublic2024-06-11 09:07
Reportergeoffclare Assigned To 
PrioritynormalSeverityObjectionTypeClarification Requested
Status ClosedResolutionAccepted As Marked 
NameGeoff Clare
OrganizationThe Open Group
User Reference
Sectiontsort
Page Number3319
Line Number111766
Interp StatusApproved
Final Accepted TextSee 0001745:0006408.
Summary0001745: tsort input and output format clarifications
DescriptionThe tsort description seems to require applications to supply a single line of input:
The application shall ensure that the input consists of pairs of items (non-empty strings) separated by <blank> characters.
However, the example shows input split over multiple lines.

It appears that most implementations accept any white-space characters as separators, although the GNU coreutils version only accepts blanks and newlines.

Also, it doesn't say whether there can be multiple separator characters between items, which all implementations I tried accept, or that the output is one-item-per-line.
Desired ActionOn page 3319 line 111766 section tsort, change:
The application shall ensure that the input consists of pairs of items (non-empty strings) separated by <blank> characters. Pairs of different items indicate ordering. Pairs of identical items indicate presence, but not ordering.
to:
The application shall ensure that the input consists of pairs of items (non-empty strings) separated by one or more <blank> or <newline> characters. It is unspecified whether other white-space characters can also be used as separators. Pairs of different items shall indicate ordering. Pairs of identical items shall indicate presence, but not ordering.

On page 3319 line 111798 section tsort, change:
The standard output shall be a text file consisting of the order list produced from the partially ordered input.
to:
The standard output shall be a text file consisting of the ordered list of items, with one item per line, produced from the partially ordered input.

Tagsapplied_after_i8d3, tc3-2008

Activities

Don Cragun

2023-07-27 16:11

manager   bugnote:0006408

Interpretation response
------------------------
The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.

Rationale:
-------------
None.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
Make the changes in the Desired Action.

agadmin

2023-07-27 16:14

administrator   bugnote:0006409

Interpretation proposed: 27 July 2023

ajosey

2023-08-31 13:29

manager   bugnote:0006438

Interpretation approved: 31 August 2023

Issue History

Date Modified Username Field Change
2023-06-13 14:32 geoffclare New Issue
2023-06-13 14:32 geoffclare Name => Geoff Clare
2023-06-13 14:32 geoffclare Organization => The Open Group
2023-06-13 14:32 geoffclare Section => tsort
2023-06-13 14:32 geoffclare Page Number => 3319
2023-06-13 14:32 geoffclare Line Number => 111766
2023-06-13 14:32 geoffclare Interp Status => ---
2023-07-27 16:11 Don Cragun Note Added: 0006408
2023-07-27 16:12 Don Cragun Final Accepted Text => See 0001745:0006408.
2023-07-27 16:12 Don Cragun Status New => Interpretation Required
2023-07-27 16:12 Don Cragun Resolution Open => Accepted As Marked
2023-07-27 16:14 agadmin Interp Status --- => Proposed
2023-07-27 16:14 agadmin Note Added: 0006409
2023-07-27 16:31 geoffclare Tag Attached: tc3-2008
2023-08-31 13:29 ajosey Interp Status Proposed => Approved
2023-08-31 13:29 ajosey Note Added: 0006438
2023-09-05 11:02 geoffclare Status Interpretation Required => Applied
2023-09-05 11:03 geoffclare Tag Attached: applied_after_i8d3
2024-06-11 09:07 agadmin Status Applied => Closed