[#28015] RCR: RUBY_VERSION_INT — Roger Pack <rogerdpack2@...>

Situation:

14 messages 2010/02/02

[#28113] [Bug #2723] $: length affects re-require time of already loaded files — Greg Hazel <redmine@...>

Bug #2723: $: length affects re-require time of already loaded files

16 messages 2010/02/08

[#28151] [Bug #2739] ruby 1.8.7 built with pthreads hangs under some circumstances — Joel Ebel <redmine@...>

Bug #2739: ruby 1.8.7 built with pthreads hangs under some circumstances

31 messages 2010/02/11

[#28188] [Bug #2750] build fails on win32/MinGW: "executable host ruby is required." even when --with-baseruby is used — Christian Bodt <redmine@...>

Bug #2750: build fails on win32/MinGW: "executable host ruby is required." even when --with-baseruby is used

9 messages 2010/02/16

[#28206] Is Math module a wrapper of libm? — Yusuke ENDOH <mame@...>

Hi matz --

23 messages 2010/02/18
[#28212] Re: Is Math module a wrapper of libm? — Yukihiro Matsumoto <matz@...> 2010/02/18

Hi,

[#28219] Re: Is Math module a wrapper of libm? — Yusuke ENDOH <mame@...> 2010/02/18

Hi,

[#28225] Re: Is Math module a wrapper of libm? — Marc-Andre Lafortune <ruby-core-mailing-list@...> 2010/02/18

Hi,

[#28233] Re: Is Math module a wrapper of libm? — Kenta Murata <muraken@...> 2010/02/18

Hi,

[#28265] Re: Is Math module a wrapper of libm? — Marc-Andre Lafortune <ruby-core-mailing-list@...> 2010/02/20

Hi,

[#28286] Re: Is Math module a wrapper of libm? — Kenta Murata <muraken@...> 2010/02/21

Hi

[#28291] Re: Is Math module a wrapper of libm? — Marc-Andre Lafortune <ruby-core-mailing-list@...> 2010/02/22

Hi!

[#28235] [Feature #2759] Regexp /g and /G options — Michael Fellinger <redmine@...>

Feature #2759: Regexp /g and /G options

35 messages 2010/02/18

[#28329] [ANN] Ruby 1.9.2dev has passed RubySpec! — Yusuke ENDOH <mame@...>

Hi,

12 messages 2010/02/24

[#28355] [ANN] Toward rich diversity of Ruby development. — Urabe Shyouhei <shyouhei@...>

A short announcement: thanks to some helps of GitHub people, I now have

12 messages 2010/02/27

[#28365] Indentifying key MRI-on-Windows issues — Jon <jon.forums@...>

In an effort to begin summarizing key MRI-on-Windows open issues I'm starting this thread in hopes that those interested will respond with details on the key MRI issues they feel need resolution for Windows users.

11 messages 2010/02/27
[#28690] Re: Indentifying key MRI-on-Windows issues — Roger Pack <rogerdpack2@...> 2010/03/16

> My key concern is http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-=

[ruby-core:28349] Re: [ANN] Ruby 1.9.2dev has passed RubySpec!

From: Yusuke ENDOH <mame@...>
Date: 2010-02-26 08:39:05 UTC
List: ruby-core #28349
Hi,

2010/2/26 Vladimir Sizikov <vsizikov@gmail.com>:
> One thing I'd like to bring an attention to is Windows support. Sorry,
> couldn't resist! :)
> There are literally thousands of failures (including hangups) when
> running RubySpec  against MRI 1.9.2 on Windows. We've fixed some of
> the RubySpec tests to be more windows-friendly or to have alternative
> tests on Windows altogether, but there is a long, long way to go
> still.
>
> Having ruby-core looking at this would be great too, since MRI
> behavior on Windows is often differs from its behavior on *nix, and in
> plenty of times it is just not clear where there is a bug and where an
> intentional change of behavior, dictated by the platform.


I know that some people really want windows support, and that you need
spec clarification.  But unfortunately, there is no committer who not
only are interested in RubySpec but also are familiar with windows.
In fact, I'm reluctantly tackling mingw but I'm now dizzy :-(

In addition, no offense to you, but RubySpec is immature as spec for
windows version of Ruby.  Many specs often forgets text mode of IO,
file path handling (e.g., separator and drive letter), IPv6 handling,
etc.
Of course, mingw version of Ruby also has many faults (I already found
some bugs by RubySpec), RubySpec result on windows has still too many
noise.
I'll fix bit by bit, we cannot officially afford to fix RubySpec and
cannot wait for improvement of RubySpec.

Time will solve the problem, but we have no time.  We should not delay
the release any longer unless serious issue is actually identified on
mswin/mingw, "best effort" platforms.

-- 
Yusuke ENDOH <mame@tsg.ne.jp>

In This Thread