LinkedList implementing both could be seen as a mistake from that
point of view. When coding to interfaces, which is good practice anyway,
this change isn't visible though.
Thoughts?
- Jonas Konrad
input code units / chars). Of course, consuming
multiple code points would be new but code points aren't really part of
the CharBuffer api.
- Jonas
On 05/02/2018 05:29 PM, Weijun Wang wrote:
On May 2, 2018, at 4:35 PM, Jonas Konrad wrote:
"0a0b0c".getBytes(HexCharset.getInstanc
eally what I mean. The interesting part about doing
this as a charset is the unified API aspect of it, the fact that you can
reuse existing code utilizing Charset for hex operations.
- Jonas
On 05/02/2018 11:44 AM, Alan Bateman wrote:
On 02/05/2018 09:35, Jonas Konrad wrote:
Hi,
Conceptual
Hi,
Conceptually, a 'charset' (in java) is a pair of transformations from
bytes to utf-16 code units and vice versa. Could it be useful to have
charset implementations that convert from bytes to the hex (or base64)
representations of those? The idea is as follows:
"0a0b0c".getBytes(HexCharse
standard library does not currently include less accurate but faster
Math functions, maybe someone else can answer if that is something to be
considered.
- Jonas Konrad
On 11/09/2017 10:00 AM, Laurent Bourgès wrote:
Hi,
The Marlin renderer (JEP265) uses few Math functions: sqrt, cbrt, acos
wish to decode a ByteBuffer, you can use the CharsetDecoder API
directly. I do not believe an asCharBuffer-like method which decodes on
the fly is possible generally for all charsets, because decoding is not
necessarily possible in a random-access buffer due to dynamic-width
encoding.
-
mprove the
wording, or if you believe it is sufficient, close the jira bug?
Thank you,
- Jonas Konrad
