isaacs e9b6b0b327 Report "weird" errors a little better. ... There are a few kinds of errors that are very confusing. 1. Errors raised in nextTick 2. Errors emitted on the "error" event 3. RangeErrors that crash the program (or anything without a stack trace) Long traces will make make these better, of course. In the meantime, this adds a few handy signposts (in the form of better error reporting and comments on the otherwise inscrutable code printed to the terminal) that can help new users find the cause, or at least, ask for help more effectively.		2010-10-02 06:44:28 -07:00
..
2100bytes.js	Update tests to work with module contexts	2010-07-15 14:21:31 -07:00
2100bytes.out	Fix message tests	2010-06-19 17:41:34 -07:00
hello_world.js	Update tests to work with module contexts	2010-07-15 14:21:31 -07:00
hello_world.out	Add message tests	2010-06-18 18:14:06 -07:00
testcfg.py	script.runIn*Context not throwing errors properly.	2010-06-19 19:31:09 -07:00
undefined_reference_in_new_context.js	Update tests to work with module contexts	2010-07-15 14:21:31 -07:00
undefined_reference_in_new_context.out	Report "weird" errors a little better.	2010-10-02 06:44:28 -07:00