I guess I was talking more about embedding APIs. The versioning problem still exists there, though.... But that can be solved by simply creating the "latest" version based on javadoc (say daily) and snapshotting it at release time so you can always look up what the API looked up in a particular release.
Well... that suggestion gives you interface documentation, indeed. It does NOT give you documentation of contracts, like: 1. who implements this interface, 2. what other interfaces does this implement (that you can rely on), 3. how you should get a component implementing this interface (for example, nsIURI and nsIMIMEInfo should not be created by contractid).
_______________________________________________
mozilla-documentation mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-documentation
