From: Curt Hibbs <ml.chibbs@...>
Date: 2006-06-24T15:25:13+09:00
Subject: Re: windows gurus i beseech you

------=_Part_36067_12498965.1151130310623
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 6/23/06, John-Mason P. Shackelford <jpshack@gmail.com> wrote:
>
> I understand from
> http://eigenclass.org/hiki.rb?ruby+1.8.5+release+schedule that our
> next release will show up in August. It may sound crazy, but I'd
> rather see no 1.8.4 stable OCI on VC6 with a ming or current VC++
> version (now that the compiler is freely available) release in August.
> If an OCI is released, extensions will have to support it given the
> size of the OCI user base. VC6 is no longer available and there are
> significant compatibility issues not among the VC++ versions and
> mingw. If we switch to yet another compiler as early as August or even
> as early as Christmas 2006 for that matter, we experience the
> compatibility issue all over again. It is not out of the question that
> a user would have to select one of three binary versions of an
> extension just to get it running on their installed OCI which, to my
> mind, is unacceptable.
>
> --
> John-Mason Shackelford
>
> Software Developer
> Pearson Educational Measurement
>
> 2510 North Dodge St.
> Iowa City, IA 52245
> ph. 319-354-9200x6214
> john-mason.shackelford@pearson.com
> http://pearsonedmeasurement.com
>
>
This is the problem. vc++6 is no longer available, yet nearly all of the
binary extensions are only available in vc++6. Last year's disaster with
vc++7 is why we returned to vc++6. However its lack of availability and the
realization that this will be an ongoing problem is why we'll be going with
mingw.

However, I was not aware (until now) of the 1.8.5 schedule. That is too soon
for a mingw release (too much work to be be done and not enough time). If
that happens, then 1.8.5 would also be a vc++6 release.

Curt

------=_Part_36067_12498965.1151130310623--