Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <47763BDE.6030704@apache.org>
Date: Sat, 29 Dec 2007 13:21:50 +0100
From: Mladen Turk <mturk@apache.org>
User-Agent: Mozilla
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: Fwd: Visual Studio 2008 and ActiveState Perl 5.10 updates
References: <47755454.7000509@rowe-clan.net>
In-Reply-To: <47755454.7000509@rowe-clan.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

William A. Rowe, Jr. wrote:
> For information only; my post today based on new research into
> Visual Studio 2008, and ActiveState Perl 5.10 binary release, over
> these last few days.
> 
> Will focus the discussion on the modperl@perl.apache.org list for
> now since it's most intricately affected (permalink)
> 

IMHO the major problem is that people don't understand the
way how msvcrt and msvcrtXX interoperates.
It is obvious that Microsoft tries to keep the msvcrt binary
compatibility (both for 32 and 64 bit), so we should do that
as well (not because Microsoft does it, but because users needs it).

I'll be strongly against any attempt to make official binaries
linked to anything beyond msvcrt.dll.
If that means that ActiveState binaries won't work with our
official binaries, well, that's their problem, not ours.

IIUC, you are on the same track ;)

Regards,
Mladen