[#11852] continuations in Ruby 1.9? — David Flanagan <david@...>
In a comment on my recent blog post
On 8/6/07, David Flanagan <david@davidflanagan.com> wrote:
[#11860] Is this really what we want? — James Edward Gray II <james@...>
I'm investigating some recent breakage in FasterCSV and have tracking
Hi,
[#11871] ruby-openssl: == incorrect for X509-Subjects — Hadmut Danisch <hadmut@...>
Hi,
[#11876] priorities of newly-created threads — David Flanagan <david@...>
Hi,
Hi,
[#11886] Core dump with simple web scraper when run via cron — Daniel Berger <Daniel.Berger@...>
Hi all,
[#11890] Ruby and Solaris door library — "Hiro Asari" <asari.ruby@...>
Hi, there. This is my first patch against ruby. I think I followed
Hiro Asari wrote:
On 8/13/07, Daniel Berger <djberg96@gmail.com> wrote:
> -----Original Message-----
On 8/15/07, Berger, Daniel <Daniel.Berger@qwest.com> wrote:
[#11893] UDP sockets raise exception on MIPS platform — Brian Candler <B.Candler@...>
I am running ruby-1.8.6 under OpenWrt (*), which is a small MIPS platform
[#11894] IO#seek and whence problem — Bertram Scharpf <lists@...>
[#11899] pack/unpack 64bit Integers — Hadmut Danisch <hadmut@...>
Hi,
On Wed, Aug 15, 2007 at 06:50:01AM +0900, Hadmut Danisch wrote:
On Wed, Aug 15, 2007 at 02:45:20PM +0900, Brian Candler wrote:
On Fri, Aug 17, 2007 at 05:17:09PM +0200, Hadmut Danisch wrote:
Dumb question of the day: are Kernel#proc and Kernel#lambda identical?
> Dumb question of the day: are Kernel#proc and Kernel#lambda identical?
[#11900] missing bison, gperf not detected, do I need ruby to build ruby? — "Gabor Szabo" <szabgab@...>
Hi,
On Wed, 15 Aug 2007, Gabor Szabo wrote:
> > It seems ./configure did not detect the fact that bison was missing from
[#11930] Bug in select? — "Robert Dober" <robert.dober@...>
Hi
[#11945] Smoke testing Ruby — "Gabor Szabo" <szabgab@...>
Hi,
On 8/21/07, Gabor Szabo <szabgab@gmail.com> wrote:
Ruby used to have the Triple-R project based on Rubicon: see
Hugh Sasse wrote:
[#11947] Splatting MatchData bug? — Jos Backus <jos@...>
$ /tmp/ruby-1.9/bin/ruby -v
[#11948] Fibers in Ruby 1.9? — David Flanagan <david@...>
I just noticed that my ruby1.9 build of August 17th includes a Fiber
David Flanagan wrote:
On 8/22/07, Daniel Berger <djberg96@gmail.com> wrote:
On Wed, 22 Aug 2007 20:50:12 +0900, "Francis Cianfrocca" <garbagecat10@gmail.com> wrote:
On 8/22/07, MenTaLguY <mental@rydia.net> wrote:
On Thu, 23 Aug 2007 00:57:01 +0900, "Francis Cianfrocca" <garbagecat10@gmail.com> wrote:
[#11960] coroutines with Fiber::Core — David Flanagan <david@...>
The following code works on Linux with today's snapshot of 1.9:
Hi,
[#11981] Inverse Square Root — "Dave Pederson" <dave.pederson@...>
Hello-
[#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.
Hi,
On Sat, 25 Aug 2007 10:54:20 +0200, Yukihiro Matsumoto
Hi,
On 8/25/07, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
Hi,
On 8/25/07, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
[#12025] how to build ruby on vms — "toni" <toni@...>
Hi,
[#12040] Pragmas in Ruby 1.9 — David Flanagan <david@...>
Hi,
[#12042] Encodings of string literals; explicit codepoint escapes? — David Flanagan <david@...>
This message contains queries that probably only Matz can answer:
Hi,
Yukihiro Matsumoto wrote:
On 8/31/07, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
Re: Fibers in Ruby 1.9?
Hi,
Charles Oliver Nutter wrote:
> Is there any documented specification for Fibers yet? I've got basic
> Fibers working in JRuby using native threads (first two tests in your
> test_fiber pass), but I'm not clear on the semantics of a few methods. I
> also don't have it working for a "normal" thread to participate as a
> fiber (i.e. Fiber.current only works within an explicitly-created fiber
> at the moment).
>
> There are also some interesting questions I have to resolve regarding
> fibers in a concurrent native-threaded VM.
>
> Pointers to documentation would be appreciated :)
I think Fiber class is not needed for most of people. Because 1.9
support Enumerator as outer iterater (I'm not sure about this
nameing) such as Java's Iterator or Python's Generator or Ruby's
'generator' library and so on.
en = 3.times # Calling Fixnum#times without
# block return Enumerator
p en.next #=> 0
p en.next #=> 1
p en.next #=> 2
p en.next #=> call exception: StroIteration
en.rewind
loop{
p en.next #=> 0, 1, 2
} # loop method catch StopIteration
Main purpose of Fiber is to realise outer iterator. In fact,
Enumerator#next using Fiber. So I think ruby/test_enumerator.rb is
more important test than implement Fiber's methods.
BTW, I can't summarise Fiber's document because I must write doctor
thesis (it's about Ruby/YARV) :) So please wait for middle of Sep.
Can Matz or someone write it?
Easy instruction:
=================
Fiber#resume
Resume Fiber's context.
Fiber.yield(...)
return values to resuming context.
example:
f = Fiber.new{
Fiber.yield 1
Fiber.yield 2
Fiber.yield 3
}
f.resume #=> 1
f.resume #=> 2
f.resume #=> 3
Fiber.current
return current fiber.
Fiber#alive?
return if this fiber is alive or not.
Fiber#transfer
tranfer fiber context. This method break resume/yield
(parent/child) relation, so we shouldn't use it (this method is
similar to callcc).
example:
f1 = Fiber.current
f2 = Fiber.new{
f3.transfer 10
}
f3 = Fiber.new{|e|
f1.transfer e + 20
}
p f1.resume #=> 30
fiber.so
If you require fiber.so, above Fiber methods are added.
This library is for professional (for what?).
continuation,so
If you require continuation.so, callcc is available.
I want to rename this library as unsafe/continuation.so
or somthing.
Regards,
--
// SASADA Koichi at atdot dot net