Closed xaderfos closed 3 years ago
@xaderfos you're absolutely right. thank you for reporting this issue! i'll try to push the fix asap
That's great, I've been testing ruxnasm in my Emacs uxntal-mode and wanted to make sure it works as smooth as uxnasm.
@xaderfos alright, should be fixed in 519b8109d4a83cd86f34bb755cbc866f53303f77.
again, thank you so much for the issue. sorry you had to wait for so long, i didn't get a notification
No worries at all! I have not been slowed down by this in any way. I'll test it as soon as I can ;)
I can confirm that this is now fixed, thank you very much for this @karolbelina ;)
This happens for me on OSX 10.15.7 with ruxnasm built from the source code.
I can see the errors and there is no rom produced but the return code is 0. This is an issue when trying to use ruxnasm from within other processes.
Expected behaviour: 0 should only be returned if the assemble was successful, greater than 0 should be returned otherwise.