[Bug 27894] New: Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

Summary: Inconsistent "for /L" parsing
           Product: Wine
           Version: 1.3.25
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cmd
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

"for /L %i in (1,2,3) do echo %i" is parsed correctly
Output:
1
2
3

while

"for /L %i in (1,1,1) do echo %i" is not
Output: 
wine: cannot find L"C:\windows\system32\do.exe"
File not found

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

Frédéric Delanoy  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download, source, testcase

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from André H.  2011-07-25 17:10:14 CDT ---
confirming, even if "for /L %i in (1,2,3) do echo %i" only outputs
1
here

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

--- Comment #2 from Frédéric Delanoy  2011-07-25 17:42:19 CDT ---
(In reply to comment #1)
> confirming, even if "for /L %i in (1,2,3) do echo %i" only outputs
> 1
> here

Right. Got the same here. Must have copied too much.

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

Jason Edmeades  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Jason Edmeades  2012-09-02 17:51:50 CDT ---
2 issues here...

1. for /L doesnt respect boundaries and often falls one short when using
'normal' numbers (should be <= and >= rather than > and <)

2. When no iterations occur, the rest of the for loop (the bit in brackets OR
the do xxxxx part) is left as the next command, so it steps on to try to
execute it

Patches submitted for both parts:
http://www.winehq.org/pipermail/wine-patches/2012-September/117422.html
http://www.winehq.org/pipermail/wine-patches/2012-September/117421.html

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from Bruno Jesus  2012-09-03 13:51:52 CDT ---
Patches commited:
http://source.winehq.org/git/wine.git/commitdiff/3a25888f38dbfed5d80368aaea4...
http://source.winehq.org/git/wine.git/commitdiff/1a9413b98a04358935424c54a73...

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

Jason Edmeades  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #5 from Jason Edmeades  2012-09-03 14:33:47 CDT ---
Resolving now change in git

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
      Fixed by SHA1|                            |3a25888f38dbfed5d80368aaea4
                   |                            |c2bd4f601dc7b

[Bug 27894] Inconsistent "for /L" parsing

http://bugs.winehq.org/show_bug.cgi?id=27894

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #6 from Alexandre Julliard  2012-09-14 13:35:19 CDT ---
Closing bugs fixed in 1.5.13.