Very strongly agree.
I also suggest that in-JavaScript diagnostics, such as access to stack
information when errors occur, is also standardized by this track.
For example, there are bugs logged against all 3 major engines about the
fact that onerror is basically useless because there's no way to get a
stack trace:
https://bugs.webkit.org/show_bug.cgi?id=55092
https://bugzilla.mozilla.org/show_bug.cgi?id=355430
https://connect.microsoft.com/IE/feedback/details/663758/no-way-to-programmatically-get-stack-trace-on-javascript-error
In each case, this has been acknowledged as a real problem, but it's fairly
clear that at least the WebKit and Firefox bugs are stalled due to lack of
standardization.
Also, more kudos to Joey and John for Source Maps :)
Cheers,
Charles
On Wed, Apr 11, 2012 at 4:30 PM, Mark S. Miller <erig...@google.com> wrote:
> Hi Joey,
>
> I'm very glad to see this and I think it should be standardized by TC39.
> However, it should not be standardized as "part of the language", and so
> would result in a document distinct from Ecma 262. A good model is the way
> the internationalization track is proceeding.
>
> Rather than create an entire new track just for source maps, I think this
> goes hand in hand with the need to standardize a debugging API. I suggest
> both be bundled into one new track.
>
>
> On Wed, Apr 11, 2012 at 11:11 AM, Joey Schorr <jsch...@gmail.com> wrote:
>
>> Greetings ES Discuss!
>>
>> We (Joey Schorr and John Lenz, CCed) are some of the authors of the
>> source map specification that is now implemented by WebKit and Firefox, as
>> well as a number of compilers (Closure Compiler, GWT and soon
>> CoffeeScript). Given that the specification is becoming a de-facto standard
>> for mapping of code which is compiled to JS, we were curious if there was
>> any interest in making it an actual standard under TC39. The current
>> specification can be found here:
>> https://docs.google.com/a/google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit,
>> with a number of contributions from all the various parties involved.
>>
>> Thanks!
>> Joey Schorr
>>
>> Additional information:
>>
>> Firefox implementation: https://github.com/mozilla/source-map
>> WebKit implementation:
>> http://code.google.com/codesearch#OAMlx_jo-ck/src/third_party/WebKit/Source/WebCore/inspector/front-end/CompilerSourceMapping.js
>> Tutorial for Chrome:
>> http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/
>>
>>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss@mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
>>
>
>
> --
> Cheers,
> --MarkM
>
> _______________________________________________
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
