-
Bug
-
Resolution: Fixed
-
P4
-
24
In various parts of the class file api where the `@jvms` tag is used as an inline tag, it is used in an idiom like:
"... as defined in {@jvms 4.7.20.2}"
This renders as
"... as defined in 4.7.20.2."
where "4.7.20.2" is a link to a the corresponding section. Elsewhere in core libs, the pattern used is
"... as defined in JVMS {@jvms 4.7.20.2}"
which renders as
"... as defined in JVMS 4.7.20.2."
which IMO is much clearer to reader.
"... as defined in {@jvms 4.7.20.2}"
This renders as
"... as defined in 4.7.20.2."
where "4.7.20.2" is a link to a the corresponding section. Elsewhere in core libs, the pattern used is
"... as defined in JVMS {@jvms 4.7.20.2}"
which renders as
"... as defined in JVMS 4.7.20.2."
which IMO is much clearer to reader.
- relates to
-
JDK-8336794 Remodel TypeAnnotation to "have" instead of "be" an Annotation
-
- Closed
-
- links to
-
Commit(master) openjdk/jdk/56dec215
-
Review(master) openjdk/jdk/20513