[ 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 14:00:52 -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=oJpuByohjx1z61wJRLaA6cMfz5W6OSwobLFu3huAM1wwjnOOqIaz+XbcTYwnHPiuV9PKNaJyDyHIPK1aeEooCOjzPohSBlyMzXYjWfosgf3K+T+dkVGHuNrtjswqoRmGMU+KliIsbX8qmoU2Tdr+9f4IqohW5gpABZacmg41JsI=
On Thursday 18 August 2005 03:34 pm, Matthew Leverton wrote:
> I recently installed the beta for VC++ 2005 Express (MSVC 8.0)
How much longer are we going to continue supporting MSVC? Since it's clear
that Microsoft doesn't want to support standards that Allegro's going to rely
on (C99), and it's working to purposely break code that uses standard
functions (by deprecating a good number of common libc functions), I think
it'd do a huge disservice to the cross-platform compatible nature of Allegro,
and the coders that work with it, to try and pander to new versions of MSVC.