Closed Bug 1073955 Opened 7 years ago Closed 7 years ago
octal literals and octal escape sequences are deprecated: ...resource://mozmill/stdlib/httpd
Comment on attachment 8496555 [details] [diff] [review] Replaced literal octal string(s) with ParseInt() call(s). Hi, I won't mind creating a new patch if 0o prefix is a preferred approach these days. TIA
Attachment #8496555 - Flags: review?(standard8)
Attachment #8496555 - Flags: review?(standard8) → review+
I wonder if we actually should fix these mozmill files. Won't they be replaced by newer mozmill anyway? Will making changes to our local mozmill not break the upgrade?
(In reply to :aceman from comment #2) > I wonder if we actually should fix these mozmill files. Won't they be > replaced by newer mozmill anyway? Will making changes to our local mozmill > not break the upgrade? I would expect the "upgrade" to be "replace existing version with the new one", not "generate patch and apply it". So I don't think it matters too much.
(and this file is gone in the latest mozmill master)
Yeah, then we should better proceed with the upgrade than wasting time on these warnings. I think Chiaki was working on the upgrade.
(In reply to :aceman from comment #5) > Yeah, then we should better proceed with the upgrade than wasting time on > these warnings. I think Chiaki was working on the upgrade. WAIT A SECOND here. I have replaced mozmill with a newer version, I thought. Last year, if I am not mistaken. Can Mark explain which version (upstream) is he talking about? Maybe I should again go ahead and make the replacement ahead of the pack. Still, I wonder why I had not noticed this issue before... Oh, is it possible that the latest update/refresh of local C-C tree replaced my NEW replacement of mozmill internally? Totally confused.
From what I can see, bug 929608 (mozmill 1.5.24) and bug 930732 (mozmill 2.0) as still unfinished and didn't produce anything landable in the trunk.
Sorry there was a misspelling and somehow JS and mozmill did not catch it (?) (I have four similar bugzilla entries/patches. Here is a template response.) Thank you for the review. I am uploading a new patch with that uses "0o" prefix for octal literal. It seems "0o..." notation is preferred over parseInt(..., 8). Regarding the misspelling of "ParseInt" for "parseint", I thought initially people were referring to the misspelling in the description field of my patch. I said "Whoa!" when I realized that the code itself had this misspelling(!) SURPRISE: I had applied the patch to my source tree, and had run the |make mozmill| test, and JS and mozmill test frame never printed a single complaint about this (!!!) That is why I did not realize the misspelling in the code portion of the patch. I carefully checked the log files and found no mention of ParseInt at all. Also, the number of failed errors were not that much different before and after the patch. (Because of timing-sensitive errors that happen during shutdown (bugs), etc., the number of failed errors may differ from one run to the other. I did not see any major errors possibly due to the "ParseInt" misspellings.) So, I think JS interpreter is doing something without aborting the execution. What gives? I think this merits a new bugzilla entry... Anyway, the simple "Use 0o prefix for octal literal" patch is uploaded. TIA
Attachment #8497242 - Flags: review?(standard8) → review+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 36.0
You need to log in before you can comment on or make changes to this bug.