"Benjamin D. Smedberg" <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> Sherry Michael wrote:
>> I've discovered the exports from xpcom.dll changed with the Mozilla
>> 1.6b1 build (my sample plugin test failed in Firefox 1.0).
>
> If you desire to be compatible with multiple versions of XPCOM, you
> must make sure to use only the *frozen* exports and interfaces. The
> frozen exports can be found in nsXPCOM.h, and the frozen interfaces
> are marked with @status FROZEN and are included in the SDK.
>
> When using the frozen API you should also define XPCOM_STRICT_API in
> your build environment.
>
> --BDS
>
Ah .. OK, that makes sense, although I did define XPCOM_STRICT_API and
got no compiler warnings -- shouldn't there be warnings for references
to unfrozed interfaces?
I found this sample in
mozilla\modules\plugin\samples\simple
so I'll have to dig into it and see where the reference to an unfrozen
interface might be.
If there is an XPCOM based plugin sample that does not violate the
XPCOM_STRICT_API rules, I would love to find it.
Thanks for the help.
_______________________________________________
Mozilla-xpcom mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-xpcom
