|
Authored by: Anonymous on Monday, April 23 2012 @ 04:13 PM EDT |
You also can't get any comments that way (which would normally be in the
javadoc).
You could extract all of the functional parts of the API, but not the comments
that say "please only use this part in situation X", or whatever. So
its not the "entire" specification of the API, because it doesn't
include the (only socially enforced) contracts about how to use it correctly.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Monday, April 23 2012 @ 06:32 PM EDT |
While the binary .class files do have the names and types of the fields, names
of the methods, and the types of the parameters and return values, the .class
files do not have the explanatory text that makes up most of the HTML
documentation.
While a lawyer might argue that an API consists of the names and types alone, a
programmer would tell you that the explanatory text is a vital part of an API,
and that changing what the explanatory text says the methods do is changing the
API.[ Reply to This | Parent | # ]
|
|
|
|
|