[#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: coroutines with Fiber::Core

From: MenTaLguY <mental@...>
Date: 2007-08-22 21:30:46 UTC
List: ruby-core #11966
On Thu, 23 Aug 2007 05:55:50 +0900, David Flanagan <david@davidflanagan.com> wrote:

>> BTW, I'm thinking about name "Fiber".  Current Fiber means
>> Semi-Coroutine.  Fiber::Core is Coroutine.  Yes, name of Fiber is
>> from Microsoft, but it's means Semi-Coroutine such as Lua's
>> coroutine and Python's generator.
> 
> How about just calling it a Coroutine?  Lua uses coroutine even though
> it is not a full coroutine.  I'd be more concerned about the method name
> yield: Fiber.yield is superficially similar, but deeply different from a
> regular ruby yield, and I think this could cause confusion.  How about
> using Fiber.return or even Fiber.coreturn?

I kind of like coreturn, actually.  It is sort of the dual to a regular
return, even.

Also, for comparison, Rubinius calls its equivalent of Fiber::Core Task;
all of the other coroutine/continuation/threading abstractions are built
atop it in Ruby code.

-mental


In This Thread