Closed
Bug 677179
Opened 13 years ago
Closed 13 years ago
Fix nsMsgResultElement definitions in idl files
Categories
(MailNews Core :: Search, defect)
MailNews Core
Search
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 8.0
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(1 file)
986 bytes,
patch
|
Bienvenu
:
review+
|
Details | Diff | Splinter Review |
In some of the work I've been doing, I've started looking at using the python version of the xpidl parser. One of the issues that I've come across is that we seem to confuse it with our definitions of nsMsgResultElement.
Firstly, nsIMsgSearchSession defines it as an interface, then nsIMsgSearchAdapter defines it as a c++ class, and there's no actual native pointer definition for it.
The current xpidl parser seems to cope with this (somehow), but I think we should just fix it - the nsIMsgSearchSession instance isn't necessary anyway, and we can alter the native pointer definition to make idl happy.
Attachment #551416 -
Flags: review?(dbienvenu)
Updated•13 years ago
|
Attachment #551416 -
Flags: review?(dbienvenu) → review+
Assignee | ||
Comment 1•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 8.0
You need to log in
before you can comment on or make changes to this bug.
Description
•