standardizing Error.stack or equivalent

[Mark S. Miller]

Not only would I hope for all of this in ES7, I would add

5) sourcemaps
6) sourcemap extension to template strings, as in that old email
7) The sourceURL as explained at <
https://developers.google.com/chrome-developer-tools/docs/javascript-debugging#breakpoints-dynamic-javascript>
or something with equivalent functionality.

The main thing needed to get this into ES7 is a champion who will put in
the time needed. That ain't me, but I'd be happy to help.

Btw, if I were looking to drop something from the list, I'd look first to
simplify #1.



On Tue, Mar 25, 2014 at 1:39 PM, John Lenz <concavelenz at gmail.com> wrote:

> 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 <erights at google.com>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 <waldron.rick at gmail.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Mar 25, 2014 at 1:38 PM, John Lenz <concavelenz at gmail.com>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
>>> es-discuss at mozilla.org
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>>>
>>
>>
>> --
>>     Cheers,
>>     --MarkM
>>
>
>


-- 
    Cheers,
    --MarkM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140325/bca22f1f/attachment.html>