The public exported functions in XPCOM will be documented as such. For example, after I land 99147, there will be a new xpcom header nsXPCOM.h which have documentation and an @status marker for each of the (3) exported public functions.
Any function that does not have an "@status frozen" line may be subject to change and you should use at your own risk. doug turner [EMAIL PROTECTED] Jon Smirl wrote: > Sounds like all of the NS_NewXXX functions need to be carefully inspected to > make sure they only call public APIs. Most of the ones in layout/content > violate this. > > I wish there was a simpler way to separate component public APIs from app > public APIs. Should all app public APIs be required to live in an IDL file? > This would allow the build process to play with the include paths and hide > the non-global component APIs from the rest of the app. > > -- > Jon Smirl > [EMAIL PROTECTED]
