On Thu, Mar 27, 2014 at 3:28 PM, Mark S. Miller wrote:
> [+google-caja-discuss]
>
> Cool. I will fix the debug.js adaptor
> a) to fix the bug Boris reported,
> b) to map the FF nested format to the v8 nested format, and
> c) to preserve this information from the v8 API so that it appears
> correc
Hey guys,
I wanted to chime in on the discussion about Error.stack standardization.
For my lil' game engine (http://lycheejs.org) I tried a couple things
out how a custom Debugger (for a binary WebSocket protocol) can be
implemented properly. I need to write an own debugger, because I'm using
I agree the loader provides a new place to inject this information.
On Mar 31, 2014 8:59 AM, "John Barton" wrote:
> My goal is more modest: to ensure that Loader/System function(s) that
> accept strings defining JS allow name parameters.
>
> We should also work out how to include source-maps. The
My goal is more modest: to ensure that Loader/System function(s) that
accept strings defining JS allow name parameters.
We should also work out how to include source-maps. The loader has the
right position to obtain the sourcemap from the server or from transcoders.
If we have API on the loader to
John did you want to propose an alternative? Maybe:
A "name" parameter for inline scripts and eval? This might work for
"sourceUrl" but might be limiting for "soureMappingUrl".
On Sun, Mar 30, 2014 at 6:25 PM, John Barton wrote:
> Hi Mark. I implemented the first sourceURL support, for Fire
Hi Mark. I implemented the first sourceURL support, for Firebug back in
the day. It's a kludge we worked out because there was no alternative. It
forces debuggers seek the ends of buffers even if they are millions of
bytes and even if the the name does not turn out to be the one the dev was
intere
sourceUrl works in chrome, with eval at least. Is displayName for function
naming?
On Mar 28, 2014 11:56 AM, "Sebastian Zartner"
wrote:
> Hi John, supposedly <
>> https://developers.google.com/chrome-developer-tools/docs/javascript-debugging#breakpoints-dynamic-javascript>
>> and <
>> http://www
>
> Hi John, supposedly <
> https://developers.google.com/chrome-developer-tools/docs/javascript-debugging#breakpoints-dynamic-javascript>
> and <
> http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/#toc-sourceurl>
> document the emerging de facto std for providing this name to the e
Notice that the eval stack trace is not very useful in the common case that
the buffer is more complex than a single line and the eval is called more
than once. For eval, new Function(), document.write(),
document.appendChild(