X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Thu, 7 Feb 2002 11:49:24 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
cc: djgpp-workers AT delorie DOT com, ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De
Subject: Re: conflicting types for bzero (gcc303)
In-Reply-To: <1013068997.9713.6.camel@bender.falconsoft.be>
Message-ID: <Pine.SUN.3.91.1020207114620.14710B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 7 Feb 2002, Tim Van Holder wrote:

> The point is that gcc only complains if you force it to use our own
> headers by explicitly listing -I$DJDIR/include on the command line.

No, it will complain if you compile a program that includes string.h and 
calls bzero/bcopy, even if you don't use any -I switches.

> If you don't do so, I assume it uses its own private version.

We cannot tell users not to use string.h in their programs.  Having 
prototypes visible to the compiler is a good programming practice; -Wall 
flags functions without prototypes, so if they use -W* switches, they 
will have a warning one way or the other.

We should fix this.