RE: [INTERNALS-WIN] RE: Compilers, SDK support roadmap

[email protected] (Garrett Serack)
Newsgroups php.internals.win
Message-ID <689781C07FB27E458C58AC967E5444532EC72C2434@NA-EXMSG-C113.redmond.corp.microsoft.com>
I should know by the end of the day what Apache will do--I think that
is a rather domineering factor--if they go with VC9, well...

Better now than later from my perspective, but we'll see what I find out.



G

-----Original Message-----
From: Pierre Joye [mailto:[email protected]]
Sent: Wednesday, July 16, 2008 9:45 AM
To: Andi Gutmans
Cc: Garrett Serack; Elizabeth M Smith; [email protected]
Subject: Re: [INTERNALS-WIN] RE: Compilers, SDK support roadmap

hi!

On Wed, Jul 16, 2008 at 6:28 PM, Andi Gutmans <[email protected]> wrote:
> That sounds reasonable although we don't have a track record building
> with VC9. But we are probably better off trying to adopt what will be
> more aligned with what's coming down the pipe in the next two years than
> staying on an older version.
> Regardless I wouldn't want to confuse people with supporting both VC8
> and VC9. We should have only two with the hope of completely dropping
> VC6 as soon as possible.

VC6 will be droped for any release after 5.3.x (5.4 or 6).

About supporting only VC9, I'm all for it with PHP 6.x. I'm not sure
about VC9 and php 5.3 as we are cruelly lacking the time to do the
necessary ports and QA checks (5.3 is about to be frozen and the final
release is expected within 3-4 months).

I would be happy with VC6/8 for 5.3 and VC9 only for php6.

An external factor is what will Apache adopt (vc8 or vc9) and when.
That may also force us to do the move sooner. This risk is the reason
why my plan includes experimental releases for VC9 builds.

Cheers,
--
Pierre

http://blog.thepimp.net | http://www.libgd.org

--
Windows Internals Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.