Jon Smirl wrote: > > Has allowing [ref] on xpidl parameters been considered? It's only impact > would be to change the h file generation in languages that provide both > pointer and reference calling conventions. > > This would be useful when converting old h files to IDL files. The old h > files commonly used reference parameters. Changing > these to pointers requires touching up every place the function is called in > the source. > > For example: > void GetXHeight([ref] out PRUint32 aResult); > generates: > NS_IMETHOD GetXHeight(PRUint32 &aResult) = 0; > > -- > Jon Smirl > [EMAIL PROTECTED]
As you may know, we support C++ references on a per type basis, not per param. I'd *much* rather see people fix the 'broken' interfaces before they are exposed via xpidl (and still within a manageable scope where the compiler's static type checking can help). This is far better than making a non-backward compatible changes to the xpidl spec and typelibs and then assuming that all the xpt consumers will change their implementations to enforce correct runtime C++ reference semantics. John.
