The following issue has been SUBMITTED. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1745 
====================================================================== 
Reported By:                geoffclare
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1745
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Geoff Clare 
Organization:               The Open Group 
User Reference:              
Section:                    tsort 
Page Number:                3319 
Line Number:                111766 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2023-06-13 14:32 UTC
Last Modified:              2023-06-13 14:32 UTC
====================================================================== 
Summary:                    tsort input and output format clarifications
Description: 
The tsort description seems to require applications to supply a single line
of input:<blockquote>The application shall ensure that the input consists
of pairs of items (non-empty strings) separated by <blank>
characters.</blockquote>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 Action: 
On page 3319 line 111766 section tsort, change:<blockquote>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.</blockquote>to:<blockquote>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.</blockquote>
On page 3319 line 111798 section tsort, change:<blockquote>The standard
output shall be a text file consisting of the order list produced from the
partially ordered input.</blockquote>to:<blockquote>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.</blockquote>

====================================================================== 

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             => ---             
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to