Use "fibers" module then. But you'd better be sure what you're doing, because it's not how node.js is supposed to work.
 
 
29.12.2013, 01:50, "Matthew Hazlett" <hazl...@gmail.com>:
I had this idea as well, to make an overloaded function of sorts and call it again after the results are in. 

But this wouldn't really help me, as the goal is to sent the output to the caller of the function that executed the process not to the.function that actually executed the process.



--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
 
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to