I'm using the latest version FoxBin2Prg v1.19.42.
When using the convertion from text to binary file (prg2bin) with an external command, errors are not returned properly to the calling command.
You can reproduce the error by downloading the attached file "_errorreport.zip", unpacking it and running the batch script runfoxbin2prg.cmd.
The third test (subdirectory test3) tries to compile the text version of a simple form and fails.
Comments: ** Comment from web user: ralfxwagner **
Hi Fernando,
I've downloaded the 1.19.43-Preview-1 and tested.
The short version: The error status is returned properly.
The long version: I need to test this on other machines as well, but it looks really promising.
Concerning your infos about expected / unexpected errors: I understand your point about recoverable / unrecoverable errors.
For my testing I for the decompilation (BIN2PRG) I use a file totally broken at the binary level (unrecoverable), while for the compilation I use a text file with duplicate objects, where each duplicate gets reported (recoverable, although the binary version cannot be generated).
As I now get the proper error status with the preview version, I can handle this "inconsistent" behaviour, so there is no hurry for a new version that behaves differently with regard to messages boxes, errors files etc.
In case you're interested I've attached another test program, that performs the following tests:
- running BIN2PRG on a file without errors
- running BIN2PRG-SHOWMSG on a file without errors
- running BIN2PRG on a file with errors
- running BIN2PRG-SHOWMSG on a file with errors
and the same with PRG2BIN.
You'll find the results in the file "test_results.html", where I've noted,
- if the message box is shown,
- if the error file is displayed,
- if the error file is written and
- the return status.
Thanks for the great help
Ralf