![]() Therefore, I do not believe it is a good idea to encourage embedders or extension authors to continue to use binary XPCOM, and we should encourage or require alternate solutions. The XPCOM string classes will be changing: see Mozilla 2/Strings.In future versions, objects may be required to implement a custom-mark routine or provide a bitmap of GC pointers to mark. For instance, for Mozilla 2 XPCOM objects will be conservatively scanned by default. In future versions, the requirements placed upon XPCOM objects may change.nsISupports is being changed to inherit from MMgc::GCFinalizable, which is not stable by design. Instead, XPCOM objects will be garbage-collected. XPCOM Interfaces will no longer be reference-counted.In Mozilla 2, the nature of XPCOM is changing significantly. This document is only discussing XPCOM used from binary code. ![]() Components.classes, Components.interfaces, registering various objects using categories and contracts, etc will not change. ![]() NOTE: The scripted reflection of the XPCOM object model will remain almost exactly as it is today. This is possible because XPCOM has methods to expose both stable (frozen) and unstable APIs using a stable ABI in ways that are safe to link against and, if proper precautions are taken, can be used in multiple versions of mozilla-based products. XPCOM is currently being used in native code by both embedders and extension authors. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |