Closed
Bug 776630
Opened 13 years ago
Closed 13 years ago
Switch comm-central from using nsnull to nullptr.
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 17.0
People
(Reporter: mconley, Assigned: mconley)
References
Details
Attachments
(1 file, 2 obsolete files)
1.77 MB,
patch
|
Details | Diff | Splinter Review |
Bug 626472 is dropping nsnull in favour of nullptr.
I talked to Ehsan, and I think the plan is to land the definition of nullptr soon, and once it's available in mozilla-central, push our patch to try, and test building it using both clang and gcc.
I'll probably get our try server to apply the removal of nsnull against our mozilla-central subdirectory, for added assurance that we still build alright.
Assignee | ||
Comment 1•13 years ago
|
||
Part 1 from Bug 626472 has landed in mozilla-central.
As per our plan, I'm going to push the Attachment 645008 [details] [diff] to try to see if we get green builds.
Comment 2•13 years ago
|
||
FWIW, nullptr is now on mozilla-central, so you guys can proceed with this whenever you want.
Assignee | ||
Comment 3•13 years ago
|
||
Ok, here are our try results:
https://tbpl.mozilla.org/?tree=Thunderbird-Try&rev=e3b12e72613a
Mostly green, but not perfect. The build failures on Windows seem to be unrelated. The bloattest crashes on Linux, and the crashes caused by Mozmill are more disturbing.
Cc'ing Irving, who's awesome at diagnosing crashes and stuff.
I'll start by poking at the Mozmill crashes.
Assignee | ||
Comment 4•13 years ago
|
||
So the crashes on mailbloat seem to also be happening on trunk (sigh, they just showed up this morning), so that appears to be unrelated.
Comment 5•13 years ago
|
||
FWIW it will be really surprising if this results in crashes etc once you get green builds...
Assignee | ||
Comment 6•13 years ago
|
||
Yeah, it turns out that other stuff landed on mozilla-central that broke us in new and wonderful ways.
I think we're getting close to sorting it all out. Anyhow, those reds on the try build can be safely ignored, and I think we're going to survive the landing.
Assignee | ||
Comment 7•13 years ago
|
||
This spills outside of mailnews, and affects everything under comm-central.
Summary: Switch mailnews from using nsnull to nullptr. → Switch comm-central from using nsnull to nullptr.
Assignee | ||
Comment 8•13 years ago
|
||
Here's an up to date conversion patch
Attachment #645008 -
Attachment is obsolete: true
Comment 9•13 years ago
|
||
Comment on attachment 647163 [details] [diff] [review]
Switch nsnull to nullptr
Review of attachment 647163 [details] [diff] [review]:
-----------------------------------------------------------------
r=philipp for calendar parts
Attachment #647163 -
Flags: review+
Assignee | ||
Comment 10•13 years ago
|
||
Mark:
My try build looks good (well, good enough, considering the current bustedness of the tree): https://tbpl.mozilla.org/?tree=Thunderbird-Try&rev=c2c1e3d40065
Fallen has confirmed that the Calendar bits look sane. I've leafed through the diff, and I don't see anything crazy. What's the protocol for a patch this big?
Should we get a swarm of people to ensure that this thing is OK, or should we just land it?
-Mike
Comment 11•13 years ago
|
||
On m-c, we just did sed -i 's/\bnsnull\b/nullptr/g' and ehsan gave me r+ for whatever that produced without manual review. It's really unlikely this could cause problems, since nsnull is currently defined to be nullptr in m-c!
Assignee | ||
Comment 12•13 years ago
|
||
Re-ran sed script to un-bitrot, and committed to comm-central as
https://hg.mozilla.org/comm-central/rev/0a10c274a1fe
Attachment #647163 -
Attachment is obsolete: true
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 17.0
You need to log in
before you can comment on or make changes to this bug.
Description
•