From: Jan W. <we...@ef...> - 2007-05-11 19:10:10
|
> I don't think this is in the same category as unreachable code. >From the point of the average, possibly non-C-expert _user_, it is. Both are a mystery for them. One is a mysterious error, and the other is a mysterious behaviour of the program he did not intend. > I don't > think inline is even a reserved word if you're not using C99, so for the > compiler to check for it and give you a warning like "warning: inline > keyword, use C99" would be a "preemptive strike". It's the wording, which matters. "Warning at line 5: inline is not a keyword if --c99 is not specified". "Syntax error at line 5." I feel this fully understandable and adequate; together with the option to switch the warning - or all this class the warnings - off (which is an another thing I'd like to see implemented in SDCC in a better way (#pragmas per line)). > It might help a few > people, but the current error message points you in the right direction. David, it was you who said in your previous post - Syntax error somewhere around that line, that's better than Error in this file somewhere - some could say that the letter points you in the right direction, too. I can't see a single reason why it could not be even more descriptive - except the developer's time. But, this is open source, isn't it. Why discouraging somebody who eventually wants to make SDCC better? Jan Waclawek |