[gs-devel] RE: More compilation warnings from pdfwrite image changes
dan at artifex.com
Fri Jun 14 21:04:09 PDT 2002
The reason that I split WARNOPT out as a separate parameter is so I can run
with it set to /W3 on my builds. I get 1729 warnings on a full Ghostscript
Note: with gcc running on casper, I see 524 warnings, not including those
for the ICC lib, in a Ghostscript build. The ICC lib adds another 326
From: gs-devel-admin at ghostscript.com
[mailto:gs-devel-admin at ghostscript.com]On Behalf Of Igor V. Melichev
Sent: Friday, June 14, 2002 8:48 AM
To: gs-devel; L. Peter Deutsch
Subject: [gs-devel] RE: More compilation warnings from pdfwrite image
> From: L. Peter Deutsch [mailto:ghost at aladdin.com]
> Sent: Friday, June 14, 2002 7:13 PM
> To: igor at artifex.com
> Subject: Re: More compilation warnings from pdfwrite image changes
> I think it would definitely be worthwhile looking in the MSVC
> for a way to turn off any very common unimportant warnings. The ones that
> seem to be most common in a MSVC6 log that someone sent me are
> and "possible loss of data".
Individual warning codes may be suppressed with "#pragma warining".
Key question is which are important ones.
Since GCC compiles with no warnings, I can conclude that
all ones from MSVC, which appear with approved GS code, are unimportant.
Is it reasonable ?
But much more I'm worried why some important warnings
are not generated with MSVC. I guess thais is due to
in msvccmd.mak . Normal level is W3.
But If I change to W3, it will generate much more.
Possibly I should set W3 and add "#pragma warning" to some header(s).
gs-devel mailing list
gs-devel at ghostscript.com
More information about the gs-devel