Re: IID Abuse

2014-03-07 Thread Neil
Benjamin Smedberg wrote: They key magic was that NS_DECLARE_STATIC_IID_ACCESSOR is specialized on the type itself and not on a dummy class. I had tried specialising on the type itself, but the way I originally did it was only a link error rather than a compile error. I had also tried templat

Re: IID Abuse

2014-03-07 Thread Benjamin Smedberg
On 3/6/2014 8:32 PM, Neil wrote: Because of the way GetIID/NS_GET_IID works, it's not very easy to get the compiler to tell you when you're doing it wrong. So far I've come up with a way to get the linker to do it. I'm trying to get the compiler to do it, but the results aren't perfect. However

Re: IID Abuse

2014-03-07 Thread Neil
L. David Baron wrote: On Friday 2014-03-07 01:32 +, Neil wrote: I noticed a couple of places that queried for a concrete class which didn't have its own IID, which means that you end up querying for the base interface instead. Does the solution we use for do_QueryFrame work here

Re: IID Abuse

2014-03-06 Thread L. David Baron
On Friday 2014-03-07 01:32 +, Neil wrote: > Because of the way GetIID/NS_GET_IID works, it's not very easy to > get the compiler to tell you when you're doing it wrong. So far I've > come up with a way to get the linker to do it. I'm trying to get the > compiler to do it, but the results aren't

IID Abuse

2014-03-06 Thread Neil
Because of the way GetIID/NS_GET_IID works, it's not very easy to get the compiler to tell you when you're doing it wrong. So far I've come up with a way to get the linker to do it. I'm trying to get the compiler to do it, but the results aren't perfect. However along the way I have noticed som