[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] MSVC 8 cl flags
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Fri, 19 Aug 2005 15:52:02 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=hc6x6pVS+841ceu8FIG6WWGCeZ0OSt64YZzc9KkzglKEQE/YNYZbHJYz04OTIjL1cOecKPY/RfatoaEo/AB29vrTelt6eTo++FIZXDN6RlUWbFBOjnJQHcvpqt1dRvENUmxHJXqXRdLJlWWN/X00pb+yeQyFAEygKsuMQwDih3M=
On Friday 19 August 2005 03:20 pm, Evert Glebbeek wrote:
> So relax, although you might see some frustrated Microsoft bashing now and
> then, plans to drop MSVC support altogether aren't very realistic, in my
> opinion.
Mine as well. If MSVC 6 and 7 work, there's no reason to purposely break them.
However, I am concerned about turning off deprecation warnings for MSVC 8,
since that would kill the warnings for the deprecated functions Allegro
already has (even though I disagree with those warnings, it's been made a
point that they're wanted for a reason). And when the 4.3 starts coming out,
where large portions of the API will be deprecated in favor of the new API, I
would like to have deprecation warnings there to alert programmers that the
new API is available.