Loading ...
Sorry, an error occurred while loading the content.

2280Re: Has JSLINT.tree changed?

Expand Messages
  • Deva Satyam
    Jun 7, 2011
    • 0 Attachment
      --- In jslint_com@yahoogroups.com, "Douglas Crockford" <douglas@...> wrote:
      >
      > --- In jslint_com@yahoogroups.com, Satyam <satyam@> wrote:
      > >
      > > I don't download the latest version of JSLint every single time so I
      > > don't now in which version it might have stopped working but the script
      > > I use to detect repeated strings is no longer working. It relied in
      > > this part of the docs:
      > >
      > > // You can obtain the parse tree that JSLint constructed while parsing. The
      > > // latest tree is kept in JSLINT.tree. A nice stringication can be produced
      > > // with
      > >
      > > // JSON.stringify(JSLINT.tree, [
      > > // 'value', 'arity', 'name', 'first',
      > > // 'second', 'third', 'block', 'else'
      > > // ], 4));
      > >
      > > Does it still apply?
      >
      > I have restored arity for literals. I had removed it because with the new type checking stuff, it had become superfluous. Please try it now.

      Works fine now, thanks.
      >
      > I am not promising stability in the tree. JSLint's first mission is to be a code quality tool. If the quest for code quality leads me to breaking the tree, I will break the tree.
      >
      Being there a good reason for doing so, I don't mind, but this seemed an oversight. After all, if the tree exists at all, it makes sense that it should have enough information to make it worth it.
    • Show all 8 messages in this topic