From: Benoit Cerrina <benoit.cerrina@...>
Date: 2001-10-05T16:00:21+09:00
Subject: [ruby-talk:22122] Re: The Windows question still remains...


"Nat Pryce" <nat.pryce@b13media.com> wrote in message
news:003901c14d32$9ac4b210$9865fea9@backpack...
> Isn't MingGW both binary and source compatible with VC++?  If that is the
> case, I would advocate MinGW, because VC++ users could use that compiler
if
> they have paid for it.  Those who have not can use GCC.
>
> I have learnt from painful experience that that non-Microsoft compilers
lag
> behind VC++ when it comes to supporting Windows APIs.  If Ruby depends on
an
> environment or compiler that is not compatible with VC++ it will never be
> able to support the latest Windows APIs until several months after they
are
> released.  However, if Ruby uses MingGW, it will be able to use extensions
> compiled with VC++, even if GCC/MinGW cannot compile those extensions
> itself.\
>

I believe that this is very sound reasonment, what needs to be done is
define what are
the appropriate compile and link flags to make gcc and vc++ compatible and
distribute
the appropriate configure and make scripts.
Benoit