Closed
Bug 1031310
Opened 10 years ago
Closed 10 years ago
remove xpcom/analysis/ directory
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla33
People
(Reporter: froydnj, Assigned: froydnj)
Details
Attachments
(1 file)
71.29 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
Dehydra is dead, and we have clang static analysis stuff to replace it. No sense in keeping old code around, right?
Flags: needinfo?(benjamin)
Comment 1•10 years ago
|
||
The only thing I'm sorta-attached to in that directory is the autogenerated XPCOM string docs. But since they were coded against dekiwiki (which we don't use anymore) and dehydra (which doesn't work any more) I guess it doesn't make sense to just keep them around out of wishful nostalgia.
Flags: needinfo?(benjamin)
Assignee | ||
Comment 2•10 years ago
|
||
The type-printer.js file was even using E4X!
Attachment #8447221 -
Flags: review?(benjamin)
Updated•10 years ago
|
Attachment #8447221 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 3•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/82c4c46374dd
Flags: in-testsuite-
Comment 4•10 years ago
|
||
This directory was actually *very* useful as a placeholder for stuff that we want to add to the clang plugin. Is there really much value in removing it? :(
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to :Ehsan Akhgari (lagging on bugmail, needinfo? me!) from comment #4) > This directory was actually *very* useful as a placeholder for stuff that we > want to add to the clang plugin. Is there really much value in removing it? > :( Is there really much value in keeping it around vs. filing bugs on the analyses we'd like to have?
https://hg.mozilla.org/mozilla-central/rev/82c4c46374dd
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
Comment 7•10 years ago
|
||
(In reply to comment #5) > (In reply to :Ehsan Akhgari (lagging on bugmail, needinfo? me!) from comment > #4) > > This directory was actually *very* useful as a placeholder for stuff that we > > want to add to the clang plugin. Is there really much value in removing it? > > :( > > Is there really much value in keeping it around vs. filing bugs on the analyses > we'd like to have? Well, the latter is obviously much better! :-)
You need to log in
before you can comment on or make changes to this bug.
Description
•