Closed
Bug 763873
Opened 14 years ago
Closed 14 years ago
avoid repeatedly accessing aRanges.Length() within ComputeRanges
Categories
(Core :: Graphics: Text, defect)
Core
Graphics: Text
Tracking
()
RESOLVED
FIXED
mozilla16
People
(Reporter: jfkthame, Assigned: jfkthame)
Details
Attachments
(1 file)
|
4.37 KB,
patch
|
jtd
:
review+
|
Details | Diff | Splinter Review |
A little micro-optimization.... it's potentially inefficient to constantly read aRanges.Length(); instead, we can keep track of the last range index in a local variable. We also don't need the initial Clear(), as ComputeRanges is always called with a freshly-constructed array.
| Assignee | ||
Updated•14 years ago
|
Attachment #632192 -
Attachment is patch: true
Attachment #632192 -
Flags: review?(jdaggett)
Updated•14 years ago
|
Attachment #632192 -
Flags: review?(jdaggett) → review+
| Assignee | ||
Comment 1•14 years ago
|
||
Assignee: nobody → jfkthame
Target Milestone: --- → mozilla16
Comment 2•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•