Dear Mr. Considine, why are two origins for error messages: GCBASIC.EXE that produces ANY.ASM and GCBASIC.EXE that produces ANY.HEX the later produces ERRORS.TXT the first not. good would be if both give the ERRORS.txt. Thank you for your answer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
GCBASIC only produces errors.txt if there is an error, that makes it easier for IDEs to detect if the program compiled successfully.
I'm not quite sure what you mean by the gcbasic.exe that produces any.hex, it should also produce any.asm. The code inside GCBASIC is like this:
- Compile the program
- If there are errors, make errors.txt and exit
- If the /A: parameter is not used, exit
- Assemble the program
- If there are errors, make errors.txt and exit
- If the /P: parameter is not used, exit
- Call the programmer to send the program to the PIC
(PS. You can call me Hugh)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Mr. Considine, why are two origins for error messages: GCBASIC.EXE that produces ANY.ASM and GCBASIC.EXE that produces ANY.HEX the later produces ERRORS.TXT the first not. good would be if both give the ERRORS.txt. Thank you for your answer.
GCBASIC only produces errors.txt if there is an error, that makes it easier for IDEs to detect if the program compiled successfully.
I'm not quite sure what you mean by the gcbasic.exe that produces any.hex, it should also produce any.asm. The code inside GCBASIC is like this:
- Compile the program
- If there are errors, make errors.txt and exit
- If the /A: parameter is not used, exit
- Assemble the program
- If there are errors, make errors.txt and exit
- If the /P: parameter is not used, exit
- Call the programmer to send the program to the PIC
(PS. You can call me Hugh)
Ok! Hugh, thanks again, I was using the term any.hex like anyfile.hex, sorry..