« Pipelines Using Fibers in Ruby 1.9 | Main | Two New Groovy Titles »

January 02, 2008

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83451c41c69e200e54fcd64c58834

Listed below are links to weblogs that reference Pipelines Using Fibers in Ruby 1.9--Part II:

Comments

Gabe

Welcome to functional programming. Try a better language.

Paolo Bonzini

Regarding your comment: "Method objects (created with the method(...) call) are duck-typed with proc objects: we can use .call(params) on both." What is the self object in method objects called like this? Is "method" automatically creating a closure for the current receiver?

Dave Thomas

Gabe:

I try lots of different languages. In fact, Haskell was my recommended "language of the year" several years ago.

Paolo:

A bound method, which this is, acts as a closure.


Dave

Leif

Thanks for the rest of the story, Dave.
(Suggested edit: s/let's us/let us/

Ahruman

This post, like the previous one, has a [/PipelineElement] instead of a [/code], breaking formatting in Safari.

Tobin

It's a little disappointing this Fiber stuff won't be included in the new Pickaxe.

Dave Thomas

Tobin:

It's already in there (and I'm adding symmetric fibers and coroutines before I finish) ... it's just that this particular escapade was too long, and didn't really fit in any of the flows. When you're bumping 900 pages, you always have to be thinking about the contribution stuff makes.

Art Vandelay

Great pair of posts. One more nit:

s/it's head/its head/

David Richards

I like seeing the functional style in an object oriented language. Gabe's hit-and-run comment seems a little juvenile, since we choose our tools based on our project. The nice thing seems to be that every time I pick up a tool, both me and my code get better.

I've "borrowed" this code wholesale for a while. I want to play around with it and make it my own. I thought I'd refactor a KMeans implementation with this kind of style. I hope that doesn't walk on your toes, Dave.

Thanks for your constant contribution.

Mediocretes

Aside from cool factor, what's the advantage to using Fibers to build the pipeline? I'm about to implement something a lot like this, but I'm not sure there's a lot of payoff to doing it this way as opposed to the obvious way.

The comments to this entry are closed.

Now in Beta

  • Programming Ruby, 3rd Edition
    Third Edition, Covering Ruby 1.9, now available
My Photo

Pragmatic Stuff

Photos

  • www.flickr.com
    This is a Flickr badge showing public photos from pragdave tagged with pragdave_badge. Make your own badge here.