Closed Bug 41385 Opened 25 years ago Closed 22 years ago

xpcom circular dependencies

Categories

(Core :: XPCOM, defect, P4)

Product:
Core
Component:
XPCOM
Platform:
All
Other
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 66759
Milestone:
Future

People

(Reporter: warrensomebody, Assigned: dbradley)

Details

(Keywords: arch)

xpcom depends on libjar libjar depends on caps and zlib caps depends on xpcom and js ugh... this is evil
Keywords: arch
cc'ing candidates. libjar depends on caps?
Reassigning to jband. I suspect jar-involvement in xpt loading.
Assignee: mccabe → jband
What are we trying to fix here? #include dependencies? link dependencies? Warren already halled me about xpti (in xpcom) using libjar. I thought I convinced him this was not a problem. xpcom has no link dependency on libjar. What is wrong with #include dependenies? Tell me why I should not just mark this invalid?
Although I believe that xpcom should not depend on libjar (or even zlib), fixing this now is not a high priority. Ideally, xpti would define an interface and callback mechanism for reading files and zlib (not libjar) would plug into that when the browser initializes. Probably an nsIStreamIO interface would work well for this (although I need to migrate it to xpcom/io first). This bug is not invalid.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
QA Contact: leger → kandrot
mass reassign of xpconnect bugs to dbradley@netscape.com
Assignee: jband → dbradley
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Priority: P3 → P4
*** This bug has been marked as a duplicate of 66759 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.