Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
v8-dev
Home
+ new post
About this group
Join this group
Message from discussion Support extracting source mapping url defined by //@ sourceMappingURL=<url> comment. (issue7045003)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Pavel Podivilov  
View profile  
 More options May 19 2011, 5:02 am
From: Pavel Podivilov <podivi...@google.com>
Date: Thu, 19 May 2011 13:02:22 +0400
Local: Thurs, May 19 2011 5:02 am
Subject: Re: Support extracting source mapping url defined by //@ sourceMappingURL=<url> comment. (issue7045003)
Print | View thread | Show original | Report this message | Find messages by this author

> I think, this change is premature.

> Does any of JS compilers actually emit such a comment? No.

We already agreed about sourceMappingURL comment with John Lenz, so it's
just a matter or time.

> And I'm sceptic that any of JS compilers will ever support emitting such
> URLs
> because application compilation and deployment are logically separate
> steps, and
> the compiler might not know, how the URL will look like. Using relative
> URLs
> might help, but that looks lame.

Compiler may emit a template that will be populated during deployment.

> To me, a better approach would be to mimic the behavior of debugging
> symbols
> loading for native applications. That is, user specifies a directory (or a
> base
> URL) for mappings, and in that dir, for each JS file a corresponding
> mapping
> file can be found, named in some predictable manner. This requires no
> support
> from a VM engine, all symbol handling can be implemented in a debugger.

In any case user will have an option to specify mappings location
explicitly.  This change is just about providing a way to do it
automatically.

I'm not blocked by this cl, so we may defer it until there is a real usage.

> On 2011/05/18 14:08:23, podivilov wrote:

>> On 2011/05/18 13:49:08, Mikhail Naganov (Chromium) wrote:
>> > On 2011/05/18 13:21:17, podivilov wrote:

>> > Can you please elaborate more on explaining why this is needed, and how
>> this
>> can
>> > be used?

>  When debugging compiled script in chrome dev tools, user will have an
>> option

> to

>> specify source mapping location and to debug sources rather then compiled

> code.

>> Also, compiler may emit //@ sourceMappingURL=<url> comment in compiled
>> script.
>> In that case we will pick up the mapping automatically.

>  Please see chrome feature request
>> http://code.google.com/p/chromium/issues/detail?id=26912.

> http://codereview.chromium.org/7045003/


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google