Open Elsklivet opened 1 year ago
After some investigation into #1, I think this issue is caused by a strictly expected ordering of arguments, where filename comes first and flags come after. Additionally, flags themselves are not parsed correctly on Windows unless they exclude the preceding -
, it seems.
Resolution of #1 will resolve this issue.
Summary
Running
rustfuck
on Windows with the-a
flag emits an error saying something about a non-existent file, and does not produce afile.asm
.Steps to Reproduce
rustfuck
on Windows 10 withcargo build --release
file.b
Brainfuck source file./rustfuck.exe -a file.b
Expected Output: Successfully assemble the given Brainfuck source into a file
file.asm
.Actual Output:
Notes
In #1, I noted that running without any flags does appear to generate an assembly file, but it does not have the same name as the output file and cannot be assembled by NASM on Windows. The README states that linking could be a problem, but I was not expecting assembly generation alone to fail.