Loading ...
Sorry, an error occurred while loading the content.
Advanced Search
Author
Subject
Message
Special notice only

Advanced Search
  • Thank you! Austin
    sandyhead25 Dec 27, 2012
  • There appears to be a new rule that looks for unnecessary parenthesis, but this rule gets confused when wrapping regex: var mhtml = true, disqualify = (mhtml) ? (/^(\s?<((pre)|(script)))/) : (/^(\s?
    sandyhead25 Dec 27, 2012
  • I have found the following code works in both my Pretty Diff application and the JSLint tool: /*prettydiff.com api.topcoms: true*/ /*license here*/ var a; //arbitrary code here /*throw away comment here*/ var b; I would have thought JSLint would throw an error for multiple uses of the "var" keyword in any single scope, but apparently not in the global scope. Austin --- In jslint...
    sandyhead25 Aug 8, 2012
  • Fetching Sponsored Content...
  • Classification: UNCLASSIFIED This following pattern is what passes in JSLint: var o = function () { ........"use strict"; ........var x = { ................large: 0, ................css: { ....................body: "botyu" ................}, ................top: "", ................color: "default" ............}, ............p = ["wer", "asdf", { ................v: "df...
    Cheney, Edward A SFC RES USAR USARC Jul 4, 2012
  • > You should be glad to know that what you find annoying is not a consideration. I am concerned instead with correctness and readability. Mixing of quotes can be a maintainability issue. In my own application I have all of my logic divided into libraries that are directly supplied to a parent container function representing the entirety of the application. Many of these library...
    sandyhead25 Jul 2, 2012
  • Would it be possible to warn on use of the "this" keyword? With exception to extending prototypes or referencing from the DOM I have never seen an efficient use of the "this" keyword. I would even go further to say that its use in writing unnecessarily obtuse circular logic is common, typically referred to as a constructor, and is harmful to learning the language. Harmful to the...
    sandyhead25 May 15, 2012
  • Ben, It is correct that functions are first class objects in JavaScript. That statement goes to the syntax and definition of functions in the language opposed to use cases. So, that said it is perfectly valid to push functions into a different function's argument. I am just saying it is unnecessarily complex. There are more direct ways to achieve the same directives. It appears...
    sandyhead25 Apr 29, 2012
  • Please do not make this an ad hominem. Whether or not I am absolutely ignorant of how to write functional code in JavaScript your point adds nothing to the technical merits of this conversation. --- In jslint_com@^$1, Max wrote: > > You might want to spend some time on Google, looking up functional > programming, what it is, what it is good for. Discover its strengths. > There is a...
    sandyhead25 Apr 29, 2012
  • While I understand the passing of functions as arguments of other functions is a common style in many frameworks it is extremely sloppy. This is an unnecessary complexity. You can easily avoid such complicated problems by not writing code this way. To your point however, there is a use case that does reflect your concern in a way that is difficult to avoid. This one case is the...
    sandyhead25 Apr 28, 2012
  • This does not appear to be a JSLint bug. It appears to be a bug with some level of application integration. I believe that would make it a JSLex problem. In order for it to be a JSLint bug there would have to be faulty output or the application would typically have to fail on each and every request due a terminal syntax error on parsing. Austin --- In jslint_com@^$1, ┬ętefan...
    sandyhead25 Apr 19, 2012