A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1563 
====================================================================== 
Reported By:                andras_farkas
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1563
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Andras Farkas 
Organization:                
User Reference:              
Section:                    what 
Page Number:                 
Line Number:                 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2022-02-18 15:07 UTC
Last Modified:              2022-04-14 16:34 UTC
====================================================================== 
Summary:                    Wording for what seem to imply odd behavior. "all
occurrences of @(#)"
====================================================================== 

---------------------------------------------------------------------- 
 (0005800) geoffclare (manager) - 2022-04-14 16:34
 https://austingroupbugs.net/view.php?id=1563#c5800 
---------------------------------------------------------------------- 
Interpretation response
------------------------
The standard states the identification strings written by <i>what</i>, and
conforming implementations must conform to this. However, concerns have
been raised about this which are being referred to the sponsor.

Rationale:
-------------
The description in the standard does not match existing practice when the
number of identification strings in a file is not one. Additionally, an
end-of-file condition was not listed as a delimiter.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------

On page 3437 line 116031 section what, change:<blockquote>The <i>what</i>
utility shall search the given files for all occurrences of the pattern
that <i>get</i> (see [xref to <i>get</i>]) substitutes for the %Z% keyword
( "@(#)" ) and shall write to standard output what follows until the first
occurrence of one of the following:
"   >   newline   \   NUL</blockquote>to:<blockquote>The <i>what</i>
utility shall search the given files for all occurrences of the pattern
that <i>get</i> (see [xref to <i>get</i>]) substitutes for the %Z% keyword
( "@(#)" ).  The <i>what</i> utility shall write to standard output what
follows until the first occurrence of one of the following: <double-quote>
('"') , <greater-than-sign> (' >') ,  <newline> , <backslash> (' \\') , 
<NUL> ('\0'), or an end-of-file condition on the input file. If not at
end-of-file, the <i>what</i> utility shall then look for the next
occurrence of "@(#)" after one of those characters.</blockquote>
On page 3437 line 116063 section what, change:<blockquote>The standard
output shall consist of the following for each <i>file</i>
operand:<pre>"%s:\n\t%s\n", <pathname>, <identification
string></pre></blockquote>to:<blockquote>For each <i>file</i> operand, the
standard output shall consist of:<pre>"%s:\n", <pathname></pre>followed by
zero or more of:<pre>"\t%s\n", <identification string></pre></blockquote> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2022-02-18 15:07 andras_farkas  New Issue                                    
2022-02-18 15:07 andras_farkas  Name                      => Andras Farkas   
2022-02-18 15:07 andras_farkas  Section                   => what            
2022-02-18 15:23 andras_farkas  Note Added: 0005684                          
2022-02-18 16:02 shware_systems Note Added: 0005686                          
2022-02-18 16:17 shware_systems Note Edited: 0005686                         
2022-02-18 19:40 kre            Note Added: 0005689                          
2022-02-21 12:09 geoffclare     Note Added: 0005697                          
2022-02-21 18:18 andras_farkas  Note Added: 0005698                          
2022-04-14 16:34 geoffclare     Note Added: 0005800                          
======================================================================


  • [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
    • [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