Folks,
I can't help but notice that what happen to the PHP development team,
the Google Chrome development team, is now happening with the OPENSSL
development team.
That is, with Microsoft pushing out a freebie compiler VS2005 (VC8)
and now VS2008 (VC9), building developments that use to work fine
with VC6, now has all kinds of issues.
This was immediate apparent with the Old MASM vs new MASM build issues
which was settled by going with NASM. That was cool.
But now I see the same issues like with the others which is more
related to VC8/VC9 vs VC6 C language support coding issues.
I guess the question is, what is the official Microsoft WIN32 C
compiler for OPENSSL now? Is VC6 still supported?
Personally, if only VC8/VC9 is supported, I don't see why it is being
enforced. There are still productions based on VC6 and the linkage to
VC8/VC9 OPENSSL can be problematic, including possibly a requirement
of Windows Manifest distribution.
Is it reasonable to propose that any openssl coder please try to
refrain from VC8/VC9 specifics?
Thanks
-- Hector
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
