From: "Laurynas Biveinis" <lauras AT softhome DOT net>
To: <djgpp AT delorie DOT com>
Subject: Re: Disabling/enabling warnings in source code
Date: Sat, 3 Apr 1999 07:19:30 +0200
Message-ID: <01be7d91$8d8cd6e0$LocalHost@Laurynas>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-4"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Reply-To: djgpp AT delorie DOT com

>No.  However, certain warnings can be avoided by changes to your
>source.  Eg, an unused function argument can be retained without a
>warning by casting to `void'.

Thank you. That is what I needed.

>In general, it's much better to fix your code to avoid the warning than
>to disable the warning.

Of course. I always compile with -Wall -W anf fix all warnings. If I 
**really** know what I am doing, I disable warning before that piece of 
code and reenable after it again.

>Is there some particular thing you want it to shut up about?
Unused function arguments. But you have already given advice, thanx for it.

Laurynas Biveinis