JDK-8154556 : Use java.nio.ByteOrder instead of boolean value
- Type: Sub-task
- Component: core-libs
- Sub-Component: java.lang.invoke
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2016-04-19
- Updated: 2017-05-17
- Resolved: 2016-04-27
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9 b117Fixed  |
Description
The ByteBuffer related VarHandle factory method on MethodHandles:
public static
VarHandle byteArrayViewVarHandle(Class<?> viewArrayClass,
boolean bigEndian) throws IllegalArgumentException
accepts a boolean value representing the endianness.
Changing that parameter to ByteOrder would make it clearer for method invocations what endianness is being requested, and further makes it easier to express native endianness (e.g. ByteOrder.nativeOrder)