Closed Bug 435242 Opened 16 years ago Closed 13 years ago

Remove NS_NewAtom usage from mailnews

Categories

(MailNews Core :: Backend, defect)

Product:
MailNews Core
Component:
Backend
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: prasad, Unassigned)

References

(
URL
)

Details

(Whiteboard: [fixed by bugs 306324 and 377319]) 

Mailnews should not use NS_NewAtom, instead it should directly use the interfaces to create and use atoms.
Why?
Oops! I missed this in the description.

NS_NewAtom is not available under the frozen linkage, so is NS_RegisterStaticAtoms.
Keywords: checkin-needed
Ah, okay. :)
Probably needs a patch, though, before requesting checkin. ;-)
Keywords: checkin-needed
Product: Core → MailNews Core
Prasad, are you working on this ?

Could someone give an example of code replacement ?
URL: http://mxr.mozilla.org/mozilla/ident?... → http://mxr.mozilla.org/comm-central/i...
Assignee: prasad → nobody
Status: ASSIGNED → NEW
(In reply to Prasad Sunkari from comment #2)
> NS_NewAtom is not available under the frozen linkage, so is
> NS_RegisterStaticAtoms.

NS_NewAtom was replaced with MsgNewAtom in bug 377319.
NS_RegisterStaticAtoms was #ifdef'd in bug 306324.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
V.Fixed, per MXR.
Status: RESOLVED → VERIFIED
Flags: in-testsuite-
Whiteboard: [fixed by bugs 306324 and 377319]
You need to log in before you can comment on or make changes to this bug.