Thanks for creating an implementation for fibers. :)
Thanks,
James
> --
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en.
>
I for one thank you Marcel. Personally I will not use this, but it will solve many people's desires and give advocates on both sides a competition rather than theory based flaming. I have heard trouble due to some v8 API stuff with handling Errors, and would love to know how you handle them.
--
--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
Wow very cool Łukasz! You actually read my mind :). I was creating this at the very same time:I ended up using [fn.length - 1] instead of push() to maintain optional arguments. I didn't think of wrapping entire modules though :).
I wonder what the best way for people playing with this to collaborate will be. I could make a wiki page on github to collect gists together?
One more word: even the API translation is hacky, it shouldn't hit performance as it adds only a little code, but I'm a somewhat concerned about translating a module each time. Preferably it should work like plain require and cache translations internally... maybe add fiberize.require('fs') ?
Regards,Łukasz
The problem with bundling is that there's many different ways you could use fibers. While making every async call become synchronous is
There's got to be loads and loads of futures libraries that could be adapted to this model.
Regards,Łukasz
On Saturday, January 22, 2011 3:46:41 PM UTC+1, Marcel wrote:Wow very cool Łukasz! You actually read my mind :). I was creating this at the very same time:I ended up using [fn.length - 1] instead of push() to maintain optional arguments. I didn't think of wrapping entire modules though :).Right, actually it tried that initially, but got confused because logging functions skip undefined elements