Closed Bug 291868 Opened 19 years ago Closed 19 years ago

Disable the variable redeclaration strict warning

Categories

(Core :: JavaScript Engine, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla1.8beta2

People

(Reporter: Gavin, Assigned: brendan)

References

Details

(Keywords: js1.5)

Attachments

(1 file)

Assignee: general → brendan
Keywords: js1.5
Priority: -- → P1
Target Milestone: --- → mozilla1.8beta2
Status: NEW → ASSIGNED
Flags: blocking1.8b2+
Attached patch fixSplinter Review
Another easy patch to get in.  Ben will love it.

/be
Attachment #182639 - Flags: review?(shaver)
Attachment #182639 - Flags: approval1.8b2+
Comment on attachment 182639 [details] [diff] [review]
fix

r=shaver.  (I wanted to make a "silence of the lambdas" joke here, but it just
wouldn't come.)
Attachment #182639 - Flags: review?(shaver) → review+
Flags: testcase-
Checked in, thanks.

/be
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Did you mean to cover code snippets like this one?
if (total == 0)
  var statusText = gAddressBookBundle.getString("noMatchFound");  
else
{
  if (total == 1)
    var statusText = gAddressBookBundle.getString("matchFound");
  else  
    var statusText = gAddressBookBundle.getFormattedString("matchesFound", [total]);
}
I meant to do what I did: remove the strict warning for a var redeclaration of
an identifier declared using var previously in the same compilation unit.

/be
Blocks: 506252
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: