Re: Source Map Standard

2012-05-03 Thread John Lenz
On Wed, Apr 11, 2012 at 11:45 AM, David Bruant wrote: > Hi, > > I am not part of TC39. > I do not really have any opinion on whether it's a good or bad idea, but > I have some questions (below): > > Le 11/04/2012 20:11, Joey Schorr a écrit : > > Greetings ES Discuss! > > > > We (Joey Schorr and J

Re: Source Map Standard

2012-04-11 Thread Mark S. Miller
On Wed, Apr 11, 2012 at 5:08 PM, Charles Kendrick wrote: > 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. > +1. These three all naturally go together. > > For example, there ar

Re: Source Map Standard

2012-04-11 Thread Charles Kendrick
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

Re: Source Map Standard

2012-04-11 Thread Mark S. Miller
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

Re: Source Map Standard

2012-04-11 Thread Joey Schorr
Correct; it would be great if we somehow solved the "bundling source map with source" problem. On Wed, Apr 11, 2012 at 3:59 PM, John J Barton wrote: > > > On Wed, Apr 11, 2012 at 12:42 PM, Joey Schorr wrote: > >> Do I have constraints in my compiler (do I need to ship in a certain >>> way)? >>>

Re: Source Map Standard

2012-04-11 Thread John J Barton
On Wed, Apr 11, 2012 at 12:42 PM, Joey Schorr wrote: > Do I have constraints in my compiler (do I need to ship in a certain way)? >> > > No, you just need to provide the source map file with your code. > This 'provide' step is a bit of a headache since it means you have to coordinate your compil

Re: Source Map Standard

2012-04-11 Thread Joey Schorr
On Wed, Apr 11, 2012 at 3:22 PM, David Bruant wrote: > Le 11/04/2012 20:11, Joey Schorr a écrit : > > 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 numb

Re: Source Map Standard

2012-04-11 Thread David Bruant
Le 11/04/2012 20:11, Joey Schorr a écrit : > 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). I

Re: Source Map Standard

2012-04-11 Thread Joey Schorr
On Wed, Apr 11, 2012 at 2:45 PM, David Bruant wrote: > Hi, > > I am not part of TC39. > I do not really have any opinion on whether it's a good or bad idea, but > I have some questions (below): > > Le 11/04/2012 20:11, Joey Schorr a écrit : > > Greetings ES Discuss! > > > > We (Joey Schorr and Jo

Re: Source Map Standard

2012-04-11 Thread David Bruant
Hi, I am not part of TC39. I do not really have any opinion on whether it's a good or bad idea, but I have some questions (below): Le 11/04/2012 20:11, Joey Schorr a écrit : > Greetings ES Discuss! > > We (Joey Schorr and John Lenz, CCed) are some of the authors of the > source map specification

Re: Source Map Standard

2012-04-11 Thread Russell Leggett
I don't know if it makes sense to become part of the language standard considering that seems like its much more related to environment/tooling than the language itself. However, I would also like to take the opportunity to say thank you, because I am really excited about source maps! - Russ On W

Source Map Standard

2012-04-11 Thread Joey Schorr
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 stan