I think lack of getInterfaces() is a bigger problem than I orginally thought. For example you can't build an object inspector (like OLEView) for XPCOM objects. OLEView works because the typelibs contain the interface list, with XPCOM there is no way to get this list unless the object supports classInfo which 99% do not.
Without this support I can't build a Javascript IDE that gives me a menu for picking off the methods on the browser objects. I also can't build a tool for automatically generating SOAP WSDL files either (my current project). XSLT can't dynamically call arbitrary interfaces, etc... "Rick Parrish" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Seriously, I think this is how the classinfo macros work to begin with > and keeping it there keeps *every* interface one vtable slot shorter. I don't think it is a crisis to expand every object's class vtable by one entry, this only happens once per class, not once per instance. We're probably looking at less than 4K of run-time memory consumption. Making every object implement classinfo is going to add fourteen vtable slots and comsume a lot more memory. -- Jon Smirl [EMAIL PROTECTED]
