(2014/12/20 5:19), Jason Orendorff wrote:
So if you go to about:config and set the javascript.options.strict pref,
you'll get warnings about accessing undefined properties.

     js> Math.TAU
     undefined
     /!\ ReferenceError: reference to undefined property Math.TAU

(It says "ReferenceError", but your code still runs normally; it really is
just a warning.)

Is anyone using this? Bug 1113380 points out that the rules about what kind
of code can cause a warning are a little weird (on purpose, I think). Maybe
it's time to retire this feature.

     https://bugzilla.mozilla.org/show_bug.cgi?id=1113380

Please speak up now, if you're still using it!

thunderbird relies on many JS source files, and
sometimes a bug creeps in, for example,

 - attributes which were set before, do not get set any more
   after a modification, and

 - some other files are still referencing the now non-existing
   attributes.

JS strict warnings are the only way for me to realize such bugs exists.
Most of the codes are written many years ago, and so frankly nobody owns them, so to speak these days.

(I also notice that there are typos that can only be uncovered by
 JS strict warnings, etc.)

From the software engneerng point of view, it is essential to keep the large amount of JS source files of TB in shape IMHO.

I use the JS strict warnings that are printed from the DEBUG build of C-C TB to find and fix remaining and newly introduced bugs in TB all the time. (The number of such warnings and errors printed during |make mozmill| tests are staggering, and I created a script to sort them and prioritize them. I see probably a few dozen different bugs and attack the most frequent or most disturbing-looking bugs/warnings first.)

TIA


-j
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform



_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to