Date:	Wed, 6 Jan 1999 11:28:17 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
cc:	Andris Pavenis <pavenis AT lanet DOT lv>, djgpp AT delorie DOT com
Subject:	Re: Announce: Allegro 3.1
In-Reply-To:	<aCwlkLBnYnk2Ewy7@talula.demon.co.uk>
Message-ID:	<Pine.SUN.3.91.990106112727.8103F-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Tue, 5 Jan 1999, Shawn Hargreaves wrote:

> Do you happen to know which warning option would turn off these
> complaints?

I don't think there is such an option.

What options does Allegro use to compile itself?

> Ok, so this is directed at the people who maintain gcc rather than
> anyone on this list, but it is something that really annoys me: why
> can't they leave the warning options alone between compiler versions?

I don't maintain GCC, but here's mu $0.02: this issue is inherently
subjective and prone to wide disagreement between people.  For
example, Richard Stallman opposes even to using -Wall as a matter of
habit, and only agreed to include -Wall on the condition that its use
won't be forced on GNU projects.

So I guess that different teams and different volunteers who work on
different versions of the compiler do whatever they feel is right,
while other teams think that something else is right...  And you get
to sort all that out.

- Raw text -