Discussion of issues related specifically to writing code for native mode devices. This includes ZBasic code as well as assembly language code and C code, both inline and standalone.
ndudman wrote:Also I switched the --verbose on and the error when missing ; is more obvious...
The ZBasic compiler doesn't detect syntax errors in the inline C or assembly code at all. Although the error output of the backend compile process will contain messages that may be useful for determining what the error was, we chose not to include that in the overall compile process output thinking that it would be more confusing than helpful since it will refer to line numbers that have nothing to do with the user-generated source code.
Note that if --keep-files is used but --verbose is not used, a file named build.log will be generated in the build directory. That file will contain the output of the backend build process - essentially what you see when you add --verbose.
I wonder though if it wouldn't be useful if the --keep-files & --verbose is specified when you double click on a c error if the generated c file was opened. Sometimes I'm opening them mself, and then clicking on the file number goes to that line nicely...
To avoid confusion the file could be opened readonly, perhaps... perhaps its not so easy to do... and of course i'm sure you have more important things... just a thought.
Ive just noticed that in Linux with ZBasic_2-6-10.zip experimental, that if I double click on the verboce avr-gcc errors it opens the temp auto generated c files, I dont remember this before, but perhaps it did...