claes.redestad at oracle.com
Thu Sep 15 08:18:29 UTC 2016
Won't be enough, though, since in JMH it appears you're also getting
the encoding from System.out (java.io.PrintStream) via reflective
On 2016-09-15 08:42, Aleksey Shipilev wrote:
> Claes pointed out that our own reflective hacks to figure out console
> encoding do not work anymore . But, we need the console encoding for
> reliably printing on the console from within different sources. Note
> that you would normally just use System.console() and its PrintWriter,
> but reality is a bit more complicated, and sometimes you need to write
> the plain char stream directly into the byte-accepting methods,
> encoding on your own.
> So, my question: should we, in the light of extended Jigsaw-solving
> crunch, provide the public Console.encoding() method that would return
> the console charset?
More information about the core-libs-dev