A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1091 ====================================================================== Reported By: Mark_Galeck Assigned To: ====================================================================== Project: 1003.1(2016)/Issue7+TC2 Issue ID: 1091 Category: Shell and Utilities Type: Error Severity: Editorial Priority: normal Status: New Name: Mark Galeck Organization: User Reference: Section: 2.10.1 Shell Grammar Lexical Conventions Page Number: 2375 Line Number: 75895-75896 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2016-10-18 11:55 UTC Last Modified: 2016-10-19 04:44 UTC ====================================================================== Summary: Some "WORD tokens" do not have "the associated command" ======================================================================
---------------------------------------------------------------------- (0003429) Mark_Galeck (reporter) - 2016-10-19 04:44 http://austingroupbugs.net/view.php?id=1091#c3429 ---------------------------------------------------------------------- Yes, and as I said in the report, there is no need to invoke any "associated command" to "for loop" or anything else. For loop, in its own section, already explains how and when to expand WORDs found during its parsing. Same with every other instance of WORD. Also, I repeat, in some cases (see for example my two previous reports, which were bogus, yes, but they contained "incomplete" word expansions), there is no such thing as "WORD tokens shall have the word expansion rules applied...". This is simply not true, regardless of when the expansion happens, because for some WORDs, all the steps in "word expansion" are not performed. Since I just repeated what I already said, I don't see how I can add to the discussion. If you still don't understand what I am saying, and what this report is about, there is nothing more I can explain better, so I will just shut up. Issue History Date Modified Username Field Change ====================================================================== 2016-10-18 11:55 Mark_Galeck New Issue 2016-10-18 11:55 Mark_Galeck Name => Mark Galeck 2016-10-18 11:55 Mark_Galeck Section => 2.10.1 Shell Grammar Lexical Conventions 2016-10-18 11:55 Mark_Galeck Page Number => 2375 2016-10-18 11:55 Mark_Galeck Line Number => 75895-75896 2016-10-18 14:48 geoffclare Note Added: 0003419 2016-10-18 15:04 Mark_Galeck Note Added: 0003421 2016-10-18 15:28 Mark_Galeck Note Added: 0003425 2016-10-18 15:55 geoffclare Note Added: 0003428 2016-10-19 04:44 Mark_Galeck Note Added: 0003429 ======================================================================
