[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] MSVC 8 cl flags
- From: Matthew Leverton <meffer@xxxxxxxxxx>
- Date: Fri, 19 Aug 2005 23:29:28 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nNSzvyrap4eBLYaLQdW8x3iHk+sY2kAuqFmZptOdbKYaXBai3EEVSCrY4Yfpoh5Un6+nW7rfTSv4qA7ROmHnP6JLwT+iwhLoP+/OHX/H4QjFnd0f9FSHCzXEAJICq8ZAnLa5N7XinkfHvhnEPJ8xeejIjHnX02kW3ad0/4aEZx0=
On 8/19/05, Michal Molhanec <michal@xxxxxxxxxx> wrote:
> Matthew Leverton wrote:
> > Second, tons of standard things are deprecated. To suppress those
> > warnings, the "/wd4996" switch should be used. However, it is not
> > present on MSVC6, so it can only be added on the MSVC7 and later
> > targets.
>
> Wouldn't be better to define _CRT_SECURE_NO_DEPRECATE ?
>
I just suggested /wd4996 because I knew it worked. If there is a
better way of doing it, then I'm all for it. I didn't mean to suggest
to disable the warnings whenever someone used Allegro, but only when
Allegro was built. If people try to compile Allegro with MSVC 8 they
will probably think it failed, because of all the warnings. For some
reason, people think warnings = didn't work. :P
If people want to disable the warnings when using Allegro on their own
project, then it should be up to them to do that.
--
Matthew Leverton