Re: [Tinycc-devel] defined twice error commented out

[Stephan Beal]

On Thu, Oct 29, 2015 at 8:23 AM, Sergey Korshunoff <address@hidden> wrote:

> Removing a valid warning is never a goid idea long-term.
A tcc message was: Error And this condition is an error only if an
initialization with diffenet values asked. In other cases it can be
only warning. And there must be a flag to supress it

(finally off the train, so i can type properly...)

To be clear: i am not a tcc dev and have no authority here. However, experience tells me that a system which does not warn when it should leads to more errors long-term (e.g. MSVC 6 does not warn for many conditions which gcc rightfully considers fatal, e.g. forgetting to return a value from a non-void function). Duplicate definitions are such a case. Even if they are identical, the fact that they're being included twice likely indicates a code structure problem and "should" emit a warning unless (as you say) they are actively suppressed. Programmers very much rely on their compilers to point out (potential) problems, with more aggressive/less lenient generally being more useful than less aggressive/more lenient.

Again, that's just my $0.02, not an authoritative answer.

--

----- stephan beal
http://wanderinghorse.net/home/stephan/

http://gplus.to/sgbeal

"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf