A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1892 
====================================================================== 
Reported By:                calestyo
Assigned To:                
====================================================================== 
Project:                    1003.1(2024)/Issue8
Issue ID:                   1892
Category:                   Shell and Utilities
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Christoph Anton Mitterer 
Organization:                
User Reference:              
Section:                    2.7 Redirection 
Page Number:                2493 
Line Number:                80966, ff. 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2024-12-12 03:40 UTC
Last Modified:              2024-12-12 15:07 UTC
====================================================================== 
Summary:                    definition of `{location}>redir-op word` does not
specify whether a qouted location is still considered part of the redirection
====================================================================== 

---------------------------------------------------------------------- 
 (0007001) geoffclare (manager) - 2024-12-12 15:07
 https://austingroupbugs.net/view.php?id=1892#c7001 
---------------------------------------------------------------------- 
The discussion here seems to have missed the relevant addition to the
grammar, namely list item 3 in 2.10.1:<blockquote>If the string contains at
least three characters, begins with a <left-curly-bracket> ('{') and ends
with a <right-curly-bracket> ('}'), and the delimiter character is one of
'<' or '>', the token identifier <b>IO_LOCATION</b> may result; if the
result is not <b>IO_LOCATION</b>, the token identifier <b>TOKEN</b> shall
result.</blockquote>
In:<pre>echo hi \{fd}>&1</pre>the string does not start with '{' and so
does not qualify for tokenisation as IO_LOCATION. The other two example
cases do, but as https://austingroupbugs.net/view.php?id=1892#c6994 points out
the behaviour is
implementation-defined and so how it is affected by any quoting <i>inside
the curly brackets</i> is for implementations to decide.

Regarding the question in the Description:

> shouldn't that rather say "If ANY PART OF n is quoted…"

Yes it should. List item 2 in 2.10.1 is:<blockquote>If the string consists
solely of digits and the delimiter character is one of '<' or '>', the
token identifier <b>IO_NUMBER</b> shall result.</blockquote>If any quoting
is present, then "the string consists solely of digits" is not true and the
condition is not satisfied. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-12-12 03:40 calestyo       New Issue                                    
2024-12-12 03:40 calestyo       Name                      => Christoph Anton
Mitterer
2024-12-12 03:40 calestyo       Section                   => 2.7 Redirection 
2024-12-12 03:40 calestyo       Page Number               => 2493            
2024-12-12 03:40 calestyo       Line Number               => 80966, ff.      
2024-12-12 05:02 larryv         Note Added: 0006994                          
2024-12-12 05:19 calestyo       Note Added: 0006995                          
2024-12-12 06:31 larryv         Note Added: 0006996                          
2024-12-12 14:40 calestyo       Note Added: 0007000                          
2024-12-12 15:07 geoffclare     Note Added: 0007001                          
======================================================================


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

Reply via email to