Closed
Bug 570416
Opened 16 years ago
Closed 16 years ago
Create a static analysis script for detecting classes which should participate in cycle collection
Categories
(Developer Infrastructure :: Source Code Analysis, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 423032
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
Let's say we have class A which participates in cycle collection.
Scenario A:
Given:
class B {
A * ptr;
// ....
};
class C {
nsCOMPtr<A> ptr;
// ...
};
class D {
nsRefPtr<A> ptr;
// ...
};
class E {
nsCOMArray<A> arr;
// ...
};
Classes B, C, D, and E also need to take part in cycle collection.
Scenario B:
Given:
class F : public A {
// a strong pointer to any object
};
Class F also needs to take part in cycle collection.
These cases should be possible to detect using a static analysis script.
Comment 1•16 years ago
|
||
Dupe of bug 423032?
| Reporter | ||
Comment 2•16 years ago
|
||
Hmm, looks like it, yes.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Blocks: static_analyses
Updated•8 years ago
|
Product: Core → Firefox Build System
Updated•4 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•