Re: Supporting end column on JSErrorReport
Ehsan Akhgari <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.jseng |
|---|---|
| Message-ID | <[email protected]> |
On 2016-05-04 11:38 AM, Jason Orendorff wrote: > I would just set the end column to the start column plus 1. OK, I guess that makes sense! > But! This would be fairly easy to fix for SyntaxErrors. Filed bug 1270354. > Keeping precise > location information around for every part of a script that could > possibly go wrong would take a ridiculous amount of memory; I doubt V8 > is really all that specific with its runtime error messages. We're not. > By comparison, if you're parsing a script and hit an error, noting the > precise location (and length) of the current token is a piece of cake. Yeah this makes perfect sense. I don't think this is a particularly crucial part of the API to support, so it's fine even if V8 exposes more info here. > On Wed, May 4, 2016 at 6:22 AM, Ehsan Akhgari <[email protected] > <mailto:[email protected]>> wrote: > > Hi everyone, > > Currently JSErrorReport doesn't have the notion of the end column, > which is > something that is exposed by the corresponding V8 data structure > (v8::Message). Is the end column something that we can easily support? > > Thanks, > -- > Ehsan > _______________________________________________ > dev-tech-js-engine mailing list > [email protected] > <mailto:[email protected]> > https://lists.mozilla.org/listinfo/dev-tech-js-engine > >