Re: [Sdcc-user] Dealing with error messages.

[Philipp K. K. <pk...@sp...>]

Am 06.02.20 um 23:46 schrieb Brad Robinson:
> Hi All,
> 
> Is there's a way to get SDCC to include the full path in error
> messages?  I've checked the manual but can't find it.
> 
> I'm trying to integrate a makefile based build into VS Code's tasks
> system but can't get the problem matcher to work when the file in
> error is built by another makefile (ie one in another directory called
> by the top-level makefile).
> 
> On the same topic, I noticed there's an option --vc that outputs MS
> style error messages.  Unfortunately the $msCompile problem matcher
> built into VSCode is rather strict about certain elements in the
> message being present and SDCC doesn't comply.  This seems to be the
> minimum for it to work:
> 
> ${msg.file}(${msg.line},${msg.pos}) : ${msg.severity} ${msg.code} :
> ${msg.message}
> 
> ie: there must be a filename, line number, character position,
> severity, code and message and the spaces between elements is
> important.
> 
> It'd be great if there was an option to generate messages with
> (optional) full paths and this message format.
> 
> Finally, it seems like the messages generated by SDCC vary in format
> somewhat. Sometimes "error", sometimes "syntax error", sometimes an
> error/warning code, sometimes not. Sometimes there's a column number
> at end of line, sometimes with the line number and sometimes not at
> all.
> 
> eg:
> 
> main.c:6:11: error: missing ')' in macro parameter list
> main.c:21: syntax error: token -> '%' ; column 1
> main.c:19: error 20: Undefined identifier '__unknown__'
> main.c:20: warning 112: function '__unknown__' implicit declaration
> 
> I'm not complaining, I really like SDCC and depend on it heavily. I
> just thought I'd point out what I've found while trying to integrate
> it into VS Code in the hopes this area can be improved.
> 
> Brad

Having better compability with VC would be good, especially as the --vc
option is already there. To ensure this isn't forgotten, I suggest you
open a feature request or bug report.

I suspect that
1) VC has been getting stricter in message parsing compared to when --vc
was first implemented
2) Mayn diagnostics have been added to SDCC since without testing with
VC (most SDCC developers work on GNU/Linux only).

Philipp