Closed Bug 274137 Opened 20 years ago Closed 19 years ago

xpidl should error if two interfaces have the same uuid

Categories

(Core :: XPCOM, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: toddf, Assigned: dbradley)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; chrome://navigator/locale/navigator.properties; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; chrome://navigator/locale/navigator.properties; rv:1.7.5) Gecko/20041107 Firefox/1.0

I created a simoIList.idl file which is a base class for my list types.
Then I created a subclass simoIPersonList.idl 

[scriptable, uuid(7d7f9d13-11f3-4ec4-9ee8-63bd1df4f950)]
interface simoIList{};

and without being careful I copied the same uuid

[scriptable, uuid(7d7f9d13-11f3-4ec4-9ee8-63bd1df4f950)]
interface simoIPersonList : simoIList{};

this gave no errors or warnings from xpidl when invoked in the following way:

xpidl -w -v -e simoIPerson.xpt -m typelib -I/home/taf2/simo2/idl
-I$(MOZDIST)/idl simoIPerson.idl

Also, xpcom crashes in js when a simoIPersonList is accessed via 

var plist = Components.classes["contractid"].createInstance();


Reproducible: Always
Steps to Reproduce:
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
In latest trunk builds xpcom crashing seems to be fixed.  There still is no good
way for a xul developer to detect whether or not a duplicate uuid used in more
then one interface file.  Although, I would say this is out of the scope of both
xpcom and xpidl... a likely canidate for a xpcom centric debugger perhaps...
Component: xpidl → XPCOM
QA Contact: pschwartau → xpcom
You need to log in before you can comment on or make changes to this bug.