opbasm 1.1 with --pyparsing can't read windows formatted paths in INCLUDE

[GoogleCodeExporter]

I'm using opbasm 1.1 from HG repository Rev. 53 (379e9b667a51) 29.08.2014.
This is a followup issue to Google code issue 3.

I tried to solve issue 3 by enabling the old parser with --pyparsing.
This solves the relative path / interpreting paths as instruction problem, but 
this mode allows path only to have linux style ("/" delimited).

Is it possible to allow both common path separators ("/" or "\") maybe as an 
additional command line option?

In this case I would be able to use the same source files on windows (with 
KCPSM6.exe or opbasm) and Linux (only opbasm).

Original issue reported on code.google.com by Paebbels on 8 Oct 2014 at 6:16

[GoogleCodeExporter]

I could not reproduce this. Backslashes work fine for me with the pyparsing 
parser on Windows. In any case, the fix for issue 3 enables correct handling of 
all path types on both platforms. All paths are converted internally to use 
forward slashes since Unix Python can't deal with backslashes and Windows 
Python works with either. This will be apparent in the log files.

Original comment by kevin.thibedeau on 8 Oct 2014 at 3:33

• Changed state: Fixed