Of course Source Maps supersede //@line. Just test twice, cut once.
/be
Nicholas Nethercote wrote:
On Mon, Feb 18, 2013 at 2:59 PM, Nicholas Nethercote
<[email protected]> wrote:
Here's a more radical thought: can we just get rid of //@line support
altogether? I see three reasons for this.
- Within Mozilla code, AFAICT it's only used in cases where it doesn't
add much. For example, from browser/components/nsBrowserGlue.js we
generate dist/bin/webapprt/chrome/webapprt/content/webapp.js, which is
the same except it has a few #ifdef-y things stripped out, and the
line number remapping provides very little value.
To clarify: it's only used in
http://mxr.mozilla.org/mozilla-central/source/config/Preprocessor.py#132,
which is "a very primitive line based preprocessor, for times when
using a C preprocessor isn't an option."
Even better: Benjamin tells me the "atline" option isn't set in the browser!
Nick
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
