Doesn't that mean that plain async methods might be missing in the generated trace?
Am 13.02.2012 09:25 schrieb "Bruno Jouhier" <[email protected]>: I had to handle this in streamline and I also did it similarly with a small callback wrapper that does the try/catch. On the other hand, I found that allocating an Error object to keep track of the source stack is very costly (a new Error call costs 400 empty object {} allocations) so I chose to generate code to track the stack trace instead. Works well but this is something you can only reasonably do by preprocessing. My little bench: https://gist.github.com/1814923 You can solve the whole EH problem (stack traces + try/catch/finally) with a preprocessor or fibers (or both combined). Bruno. On Feb 13, 1:54 am, Juraj Vitko <[email protected]> wrote: > Wow, I did not know about domains.... -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
