RFR: 8353197: Document preconditions for JavaLangAccess methods [v2]

Alan Bateman alanb at openjdk.org
Wed May 7 07:55:16 UTC 2025


On Wed, 7 May 2025 07:29:55 GMT, Volkan Yazici <vyazici at openjdk.org> wrote:

>> Document preconditions on certain `JavaLangAccess` methods that use operations either unsafe and/or without range checks.
>
> Volkan Yazici has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Fix typo in pre-existing JavaDoc

src/java.base/share/classes/jdk/internal/access/JavaLangAccess.java line 332:

> 330:      * <p>
> 331:      * This method throws {@code CharacterCodingException} instead of replacing
> 332:      * when malformed input or unmappable characters are encountered.

Do we have a JBS issue to track renaming the "no replacement" methods? The naming has confused several people as not everyone is familiar with coding error actions.  Here, "no replacement" actually means that coding errors are reported.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/24982#discussion_r2077022991


More information about the security-dev mailing list