A Nicer Way to STOP with Failed Tests
As mentioned by a user in this comment, the traceback generally produced by many compilers when encountering an error stop
statement can give the false impression that the code crashed rather than finishing as expected when a test fails. While at the time I was under the impression that error stop
would be the most portable way of signaling an exit code to any process that was executing (namely since Windows exit codes are different), perhaps the user experience aspects make this worth revisiting.
As suggested in the above mentioned thread, stop 1
may be the appropriate way to do this. Some experimentation should be done to verify this works as expected for most compiler and OS combinations.
@Carltoffel, let's continue that discussion here.