Closed Bug 10693 Opened 20 years ago Closed 20 years ago

incorrect ID leads to no interface generation

Categories

(Core :: XPCOM, defect, P3, minor)

x86
Windows NT
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: jtsay, Assigned: mike+mozilla)

Details

If you use an invalid IID in the interface properties line, no class declaration
is generated, and there is no warning.

[scriptable, uuid(77772C3A2-452A-11d3-9AE1-B085B4B41855)] <= note extra digit
interface jtIIDContainer : nsISupports {
    attribute nsIDPtr containedID;
};

generates (with xpidl -m header -I c:\mozilla\xpcom\base jtIIDContainer.idl)

/*
 * DO NOT EDIT.  THIS FILE IS GENERATED FROM jtIIDContainer.idl
 */

#ifndef __gen_jtIIDContainer_h__
#define __gen_jtIIDContainer_h__

#include "nsISupports.h"
#include "nsrootidl.h"

/* starting interface:    jtIIDContainer */

ONLY!

but removing the leading 7 from the ID results in the expected header.
oops, the command-line DID in fact have the -w option too.
Status: NEW → ASSIGNED
Ew.  Thanks for catching this.

Marking as assigned.
I have code to fix this in my tree; waiting for an open tree to land it.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Fix checked in.   I also have a fix pending to tighten up the uuid parsing
routines a little.  Thanks for catching this.
Component: xpidl → XPCOM
QA Contact: mike+mozilla → xpcom
You need to log in before you can comment on or make changes to this bug.