sac2c generates error messages in unhelpful format

Bugzilla Link	920
Created on	Feb 23, 2012 09:34
Resolution	FIXED
Resolved on	Sep 26, 2015 17:22
Version	svn
OS	Linux
Architecture	PC

Extended Description

Integrated edit/compile/run development environments
help to increase programmer productivity and enjoyment.
To this end it is essential that editors can parse
the compiler generated error messages.
Here SAC is the spanner in the works as it uses an
idiosyncratic error reporting format.
SAC should not be so stubborn (NIHS) and simply use
what others have come up with.
For instance gcc uses the following format:
getopt.c: In function 'getopt_sac':
getopt.c:171: warning: passing argument 1 of 'free' discards qualifiers from pointer target type
Editors recognize this and direct the programmer
to the exact place of offense immediately.
When more errors are found the programmer can
continue to the next error with one key press.
This makes fixing errors almost automatic,
reduces typing and RSI, and leaves more time
for the wife-'n-kids... :-)