Do you want to make classInfo a required interface? I really think getInterfaces() needs to be a required interface. classInfo burns 14 vtable entries per object class and will probably add something around 100K to the memory footprint. I was hoping you could work out a scheme for doing queryInterface and getInterface off from the same table and add very little to the footprint. One macro might be able to generate both methods.
One scheme for marking things like thread safety and content-scriptability would be to add a zero method interface to the object. You could then queryInterface or getInterfaces for it. If it is there the attribute is supported. -- Jon Smirl [EMAIL PROTECTED]
