Interesting sourcemap usage. But is there any hope for standardization of the existing stack handling for ES7? It wasn't clear to me why it stalled for ES6. There a few things I would like to see: 1) standardization V8's Error.captureStackTrace API 2) standardization of the stack format 3) standardizaton of when the stack is added to the Error object (creation vs throw) 4) specification as to whether throw (and re-throw) overwrite any existing stack property
More would be welcome but that is what I would actually have an immediate use for. On Tue, Mar 25, 2014 at 11:43 AM, Mark S. Miller <[email protected]> wrote: > Hi John, see also my message at < > https://mail.mozilla.org/pipermail/es-discuss/2014-March/036642.html> > which cites some of your work on sourcemaps. > > > On Tue, Mar 25, 2014 at 11:25 AM, Rick Waldron <[email protected]>wrote: > >> >> >> >> On Tue, Mar 25, 2014 at 1:38 PM, John Lenz <[email protected]> wrote: >> >>> I was recently modifying some code to be strict mode compliant and it >>> reminded me that the primary use of the Function caller property and >>> arguments.caller is to build stack traces. Now the latest Internet >>> Explorer releases have support for stack traces, as of course do Chrome, >>> FF, and Safari but only Chrome/V8, to my knowledge, has an actual API. >>> >>> I know there was some initial work in this area and nothing is likely to >>> happen in the ES6 time frame but can something to be done to make the >>> stacks traces more usable? >>> >> >> Take a look at the work Erik Arvidsson has done so far: >> >> http://wiki.ecmascript.org/doku.php?id=strawman:error_stack >> >> >> Rick >> >> >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss >> >> > > > -- > Cheers, > --MarkM >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
