762436 - Get rid of the nsresult return value for nsIXPCScriptable::GetScriptableFlags()

Status: RESOLVED FIXED

(Core :: XPConnect, defect)

Description

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

Attachment: Patch v1

PCOM--

Comment 1

[Bobby Holley (:bholley)]

Comment on attachment 630922 [details] [diff] [review]
Patch v1

Peter and I weren't sure whether we wanted this change given the potential breakage to embedders who might be using it (are there any?). Escalating to blake.

Also, needs an IID rev.

Comment 2

[Blake Kaplan (:mrbkap) (inactive)]

Comment on attachment 630922 [details] [diff] [review]
Patch v1

Review of attachment 630922 [details] [diff] [review]:
-----------------------------------------------------------------

I say we go for it... We don't know of any XPConnect users from C++, and the IID change should save them from getting shot in the foot (it is unfortunate the nsresult and PRUint32 are the same type, but there isn't much we can do about it). This has also been bothering me for a long time so I'm super happy to see it go.

::: js/xpconnect/idl/nsIXPCScriptable.idl
@@ +79,5 @@
>      // with this bit set.
>      const PRUint32 RESERVED                         = 1 << 31;
>  
>      readonly attribute string   className;
> +    [notxpcom,noscript,nostdcall] PRUint32 getScriptableFlags();

No need for noscript here: the entire interface is noscript.

Also, as you noted, this needs an IID rev.

On a related note: is there any reason to keep this interface in IDL? Since we already have xpc_map_end.h the autogenerated macros don't seem terribly useful...

Comment 3

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

https://hg.mozilla.org/mozilla-central/rev/06565eca4487