Return values from callbacks?
# Brendan Eich (13 years ago)
See dherman's taskjs.org for one way that ES6 will support, but which requires expliciti 'yield' usage when you "wrap" to make the preemption point clear.
See dherman's http://taskjs.org/ for one way that ES6 will support, but which requires expliciti 'yield' usage when you "wrap" to make the preemption point clear. /be Hemanth H.M wrote: > Hello Hackers, > > If there was a easy way to wrap an asynchronous in a synchronous API > would it not be easy? Because we can wrap it that way any API will > need to accept a callback to return proceed values. > > I bit be speaking absolute non sense here, but just felt something > like that might makes things easier, while I was coding THIS > <https://github.com/hemanth/node-rsj/commit/051c6c45c15e2cebc88dae20b28ffe3335823335> > > -- > /'I am what I am because of who we all are'/ > h3manth.com <http://www.h3manth.com> > /-- Hemanth HM/ > _______________________________________________ > es-discuss mailing list > es-discuss at mozilla.org > https://mail.mozilla.org/listinfo/es-discuss
# Hemanth H.M (13 years ago)
WOW! Ok, thank you.
WOW! Ok, thank you. On Thu, Jun 21, 2012 at 8:32 PM, Brendan Eich <brendan at mozilla.org> wrote: > See dherman's http://taskjs.org/ for one way that ES6 will support, but > which requires expliciti 'yield' usage when you "wrap" to make the > preemption point clear. > > /be > > Hemanth H.M wrote: > >> Hello Hackers, >> >> If there was a easy way to wrap an asynchronous in a synchronous API >> would it not be easy? Because we can wrap it that way any API will need to >> accept a callback to return proceed values. >> >> I bit be speaking absolute non sense here, but just felt something like >> that might makes things easier, while I was coding THIS < >> https://github.com/hemanth/**node-rsj/commit/** >> 051c6c45c15e2cebc88dae20b28ffe**3335823335<https://github.com/hemanth/node-rsj/commit/051c6c45c15e2cebc88dae20b28ffe3335823335> >> > >> >> -- >> /'I am what I am because of who we all are'/ >> h3manth.com <http://www.h3manth.com> >> /-- Hemanth HM/ >> ______________________________**_________________ >> es-discuss mailing list >> es-discuss at mozilla.org >> https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss> >> > -- *'I am what I am because of who we all are'* h3manth.com <http://www.h3manth.com> *-- Hemanth HM * -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20120621/1a3fc710/attachment.html>
Hello Hackers,
If there was a easy way to wrap an asynchronous in a synchronous API would it not be easy? Because we can wrap it that way any API will need to accept a callback to return proceed values.
I bit be speaking absolute non sense here, but just felt something like that might makes things easier, while I was coding THIShemanth/node-rsj/commit/051c6c45c15e2cebc88dae20b28ffe3335823335