A NOTE has been added to this issue. 
Reported By:                Mark_Galeck
Assigned To:                
Project:                    1003.1(2016)/Issue7+TC2
Issue ID:                   1084
Category:                   Shell and Utilities
Type:                       Error
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Mark Galeck 
User Reference:              
Section:                    2.3 Token Recognition 
Page Number:                2347-2348 
Line Number:                74761-74780 
Interp Status:              --- 
Final Accepted Text:         
Date Submitted:             2016-10-12 08:56 UTC
Last Modified:              2016-10-15 01:31 UTC
Summary:                    rule 3, 4, 5 do not say that a token is started, if

 (0003417) Mark_Galeck (reporter) - 2016-10-15 01:31
Before I reply, I want to clarify something.  It is not my intention to
argue on any of my reports - I will accept any reply and resolution , even
if I disagree personally, so long as:

1.  The reply answers questions that were left unanswered in the current
standard, as explained in the report.  This includes pointing to a place in
the standard, if I missed it.

2.  The reply states the facts correctly that are in the standard and does
not contradict the standard.  

So, you don't have to spend your valuable time arguing your points with me.
 I will take them as granted so long as they satisfy 1 and 2 above.  All
you have to do is satisfy 1 and 2 and that is it.  

This reply IMHO does not satisfy condition 2.  I will explain why:

>Rule 3, 4, 5 basically apply once a token is started
No that is impossible, the whole thing would not work if that were the

  Rule 3 must apply in a case like 


When the current character is "f", Rule 3 must apply.  If not, and as you
say, Rule 10 applied, then the previous token would not be delimited,
because Rule 10 does not say to delimit it.

Rule 4 must apply in a case like


if it did not and only Rule 10 applied, then Rule 10 would start the word,
and then after that, we have a current token, so when the second ' is seen,
Rule 4 would apply and according to that rule the text 'bar' would be
quoted, which is false.

Rule 5 must apply in a case like


If Rule 10 applied at the first $ , then Rule 5 would apply at the second
$, identifying '$#' as a parameter expansion, elsewhere in the standard it
is explained that would yield the string '0', and then we would have the
simple command '$0'.  But that is not the intent of the standard and that
is not how existing shells behave:  they yield the simple command such as

Issue History 
Date Modified    Username       Field                    Change               
2016-10-12 08:56 Mark_Galeck    New Issue                                    
2016-10-12 08:56 Mark_Galeck    Name                      => Mark Galeck     
2016-10-12 08:56 Mark_Galeck    Section                   => 2.3 Token
2016-10-12 08:56 Mark_Galeck    Page Number               => 2347-2348       
2016-10-12 08:56 Mark_Galeck    Line Number               => 74761-74780     
2016-10-12 23:29 shware_systems Note Added: 0003408                          
2016-10-13 01:44 Mark_Galeck    Note Added: 0003409                          
2016-10-14 22:16 shware_systems Note Added: 0003416                          
2016-10-15 01:31 Mark_Galeck    Note Added: 0003417                          

Reply via email to