@Brandon, I was just looking at your tracer tool and I realized that it would be an awesome debug tool to find out when some data was getting clobbered. Could it show a stack trace on changes?
You should consider a tool that is optimized for debugging by breaking on data changes. I use the webkit inspector to break on DOM changes and it would be great to be able to break on general data (property) changes. For debugging purposes even non-objects could be traced by temporarily refactoring them into an object property in the source. Was tracer developed for debugging, or for the purpose of building things on top of it? -- 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
