RFR: JDK-8316972: Add javadoc support for restricted methods

Maurizio Cimadamore mcimadamore at openjdk.org
Mon Oct 16 16:06:36 UTC 2023


On Fri, 13 Oct 2023 16:21:48 GMT, Hannes Wallnöfer <hannesw at openjdk.org> wrote:

> Please review a change to add support for restricted methods to JavaDoc. The bulk of this patch was contributed by @mcimadamore. It adds a warning note to the summary and details of restricted methods and a superscript to links to restricted methods, similar to what we already do with elements belonging to preview APIs. I added a summary page to list all restricted methods as well as a test.
> 
> To see the wording of this feature in context, the relevant parts of generated documentation can be reviewed here:
> 
> - [Method summary](https://cr.openjdk.org/~hannesw/8316972/api.00/java.base/java/lang/foreign/AddressLayout.html#method-summary)
> - [Method details](https://cr.openjdk.org/~hannesw/8316972/api.00/java.base/java/lang/foreign/AddressLayout.html#withTargetLayout(java.lang.foreign.MemoryLayout))
> - [Restricted Methods list](https://cr.openjdk.org/~hannesw/8316972/api.00/restricted-list.html)
> - [Restricted Methods help section](https://cr.openjdk.org/~hannesw/8316972/api.00/help-doc.html#restricted)
> 
> Since the messages for deprecated, preview, and restricted elements all use the same CSS in our default stylesheet, I decided to combine them into a single CSS rule. It is still possible to define distinct styles for these features in user-provided stylesheets.

After discussing with Alex, the recommended text for the method details is:


<name> is a restricted method of the Java platform.
Programs can only use <name> when access to restricted methods is enabled.
Restricted methods are unsafe, and, if used incorrectly, might crash the JVM or result in memory corruption.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/16188#issuecomment-1764805760


More information about the javadoc-dev mailing list