[#11890] Ruby and Solaris door library — "Hiro Asari" <asari.ruby@...>

Hi, there. This is my first patch against ruby. I think I followed

19 messages 2007/08/13
[#11892] Re: Ruby and Solaris door library — Daniel Berger <djberg96@...> 2007/08/14

Hiro Asari wrote:

[#11899] pack/unpack 64bit Integers — Hadmut Danisch <hadmut@...>

Hi,

13 messages 2007/08/14
[#11903] Re: pack/unpack 64bit Integers — Brian Candler <B.Candler@...> 2007/08/15

On Wed, Aug 15, 2007 at 06:50:01AM +0900, Hadmut Danisch wrote:

[#11948] Fibers in Ruby 1.9? — David Flanagan <david@...>

I just noticed that my ruby1.9 build of August 17th includes a Fiber

22 messages 2007/08/22
[#11949] Re: Fibers in Ruby 1.9? — Daniel Berger <djberg96@...> 2007/08/22

David Flanagan wrote:

[#11950] Re: Fibers in Ruby 1.9? — "Francis Cianfrocca" <garbagecat10@...> 2007/08/22

On 8/22/07, Daniel Berger <djberg96@gmail.com> wrote:

[#11952] Re: Fibers in Ruby 1.9? — MenTaLguY <mental@...> 2007/08/22

On Wed, 22 Aug 2007 20:50:12 +0900, "Francis Cianfrocca" <garbagecat10@gmail.com> wrote:

[#11988] String#length not working properly in Ruby 1.9 — "Vincent Isambart" <vincent.isambart@...>

I saw that Matz just merged his M17N implementation in the trunk.

17 messages 2007/08/25
[#11991] Re: String#length not working properly in Ruby 1.9 — "Michael Neumann" <mneumann@...> 2007/08/25

On Sat, 25 Aug 2007 10:54:20 +0200, Yukihiro Matsumoto

[#11992] Re: String#length not working properly in Ruby 1.9 — Yukihiro Matsumoto <matz@...> 2007/08/25

Hi,

[#12042] Encodings of string literals; explicit codepoint escapes? — David Flanagan <david@...>

This message contains queries that probably only Matz can answer:

16 messages 2007/08/31
[#12043] Re: Encodings of string literals; explicit codepoint escapes? — Yukihiro Matsumoto <matz@...> 2007/08/31

Hi,

Re: Smoke testing Ruby

From: Hugh Sasse <hgs@...>
Date: 2007-08-29 15:25:29 UTC
List: ruby-core #12024
On Wed, 29 Aug 2007, Charles Oliver Nutter wrote:

> M. Edward (Ed) Borasky wrote:
> > I thought that was the plan -- a merge of all the Ruby test suites,
        [...]
> 
> My attempts to make this happen generally ran into the following roadblocks:
> 
> - everyone wants to use a different testing framework (test/unit, miniunit,
> rspec, minispec, runit, minirunit) and refuses to yield (though we're more
> than happy to eliminate all our minirunit stuff)
> - everyone has a different idea how to structure tests...one file per
> class-under test, one file per class/method combination, one file per related
> behavior in a given class, and so on
> - everyone wants to be a hero and "own" their wonderful test suite

Isn't this where Matz gets to use his casting vote? :-)  Iff he
decides not to, then he could nominate a proxy, perhaps?  I'm not
about to tell him how to do things: this is just a suggestion of one
way to move things forward, in the hope someone thinks of a better
way.  Deciding this is necessary, and doing so democratically is
difficult because we can't be sure everyone is included who needs to
be included, has had their say, etc.  But it would be a real shame
if this stopped progress on something which would be very supportive
of Ruby development.

        Hugh

In This Thread