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

1748Re: New Edition

Expand Messages
  • Douglas Crockford
    Jan 10, 2011
    • 0 Attachment
      --- In jslint_com@yahoogroups.com, "Jordan" <ljharb@...> wrote:
      > Removing the eqeqeq and immed option prevents me from being able to use things such as:
      > var ie = "\v"=="v"; per http://ajaxian.com/archives/ievv
      > as well as a one-line browser selector:
      > (function x(){})[-5]=='x'?'FF3':(function x(){})[-6]=='x'?'FF2':/a/[-1]=='a'?'FF':'\v'=='v'?'IE':/a/.__proto__=='//'?'Saf':/s/.test(/a/.toString)?'Chr':!!window.opera?'Op':'Unknown';
      > per http://www.thespanner.co.uk/2009/01/29/detecting-browsers-javascript-hacks/
      > These may be hacks, and I always try to avoid using them, but I've found them necessary for dealing with certain browser behaviors, and more useful than user-agent sniffing. I certainly appreciate that these options should be set for all new code and 99% of old code, but the benefit of having them as options means I can set jslint directives in my file, and continue to easily validate.
      > If you are going to insist on removing these configuration options, perhaps could you add a web get parameter so I can view the website with the latest version of jslint that offers these options?

      Clearly code quality is not important to you, or you would not be demanding your right to write incompetent crap.
    • Show all 12 messages in this topic