Closed
Bug 229589
Opened 21 years ago
Closed 19 years ago
nsBaseHashtable::Init documentation is outdated
Categories
(Core :: XPCOM, defect, P4)
Tracking
()
RESOLVED
FIXED
People
(Reporter: Biesinger, Assigned: benjamin)
References
()
Details
(Keywords: fixed1.8)
Attachments
(1 file)
2.37 KB,
patch
|
dougt
:
review+
mtschrep
:
approval1.8b5+
|
Details | Diff | Splinter Review |
92 * Initialize the object. 93 * @param initSize the initial number of buckets in the hashtable, 94 * default 16 95 * @param threadSafe whether to provide read/write 96 * locking on all class methods 97 * @return PR_TRUE if the object was initialized properly. 98 */ 99 PRBool Init(PRUint32 initSize = PL_DHASH_MIN_SIZE) obviously, there is no threadSafe parameter.
Reporter | ||
Comment 1•21 years ago
|
||
also, same file, comment above nsBaseHashtable decl: 72 * destruction. Thread-safety is optional, via a flag in Init()
Assignee | ||
Updated•19 years ago
|
Assignee | ||
Comment 2•19 years ago
|
||
Attachment #197457 -
Flags: review?(dougt)
Comment 3•19 years ago
|
||
Comment on attachment 197457 [details] [diff] [review] Remove obsolete threadsafety javadocs. lost the period on the last comment change.
Attachment #197457 -
Flags: review?(dougt) → review+
Assignee | ||
Comment 4•19 years ago
|
||
Comment on attachment 197457 [details] [diff] [review] Remove obsolete threadsafety javadocs. This is doc-only, so it should be absolutely safe and would be nice to get on the branch for the 1.8 SDK.
Attachment #197457 -
Flags: approval1.8b5?
Assignee | ||
Comment 5•19 years ago
|
||
fixed on trunk
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 6•19 years ago
|
||
Comment on attachment 197457 [details] [diff] [review] Remove obsolete threadsafety javadocs. Approved per 9/26 bug triage meeting.
Attachment #197457 -
Flags: approval1.8b5? → approval1.8b5+
Updated•19 years ago
|
Flags: blocking1.8b5+
Assignee | ||
Comment 7•19 years ago
|
||
Fixed on 1.8 branch.
Keywords: helpwanted → fixed1.8
Whiteboard: [good first bug]
You need to log in
before you can comment on or make changes to this bug.
Description
•