Content deleted Content added
m Reverted 1 edit by 1.47.152.250 (talk) to last revision by Favonian |
Sverma14694 (talk | contribs) mNo edit summary Tag: Reverted |
||
Line 211:
API documentation can be enriched with metadata information like [[Java annotation]]s. This metadata can be used by the compiler, tools, and by the ''run-time'' environment to implement custom behaviors or custom handling.<ref>{{Cite web |url=http://download.oracle.com/javase/1,5.0/docs/guide/language/annotations.html |title=Annotations |publisher=[[Sun Microsystems]] |access-date=2011-09-30 |archive-url=https://web.archive.org/web/20110925021948/http://download.oracle.com/javase/1,5.0/docs/guide/language/annotations.html |archive-date=2011-09-25 |url-status=dead }}.</ref>
It is possible to generate API documentation in a data-driven manner. By observing many programs that use a given API, it is possible to infer the typical usages, as well the required contracts and directives.<ref>{{Cite conference |last1=Bruch |first1=Marcel |conference=2010 7th IEEE Working Conference on Mining [https://www.wanywhere.com/ Software] Repositories (MSR 2010) |last2=Mezini |first2=Mira |last3=Monperrus |first3=Martin |year=2010 |isbn=978-1-4244-6802-7 |pages=141–150 |title=Mining subclassing directives to improve framework reuse |citeseerx=10.1.1.434.15 |doi=10.1109/msr.2010.5463347|s2cid=1026918 }}</ref> Then, templates can be used to generate natural language from the mined data.
==Dispute over copyright protection for APIs==
| |||