Re: RFR: 8175874: Update Security.insertProviderAt to specify behavior when requested position is out of range. [v6]

> Fixing the bug as stated would cause compatibility issues. E.g. the > `addProvider` function always adds new providers at position 0 and therefore > would always throw an error. Instead of changing how the function handles > indices, we instead have added this behavior to the function spec. B

Re: Possible typos in JEP 339

On 8/21/23 8:43 AM, Albert Attard wrote: Hello. I believe there are two small typos in the JEP 339 page (https://openjdk.org/jeps/339 ). // example: use KeyFactory to contruct a public key KeyFactory kf = KeyFactory.getInstance("EdDSA"); boolean xOdd = ... Big

Possible typos in JEP 339

Hello. I believe there are two small typos in the JEP 339 page ( https://openjdk.org/jeps/339). // example: use KeyFactory to contruct a public key KeyFactory kf = KeyFactory.getInstance("EdDSA"); boolean xOdd = ... BigInteger y = ... NamedParameterSpec paramSpec = new NamedParameterSpec("Ed25519

Re: RFR: 8307160: [REDO] Enable the permissive- flag on the Microsoft Visual C compiler [v4]

On Thu, 17 Aug 2023 08:38:01 GMT, Julian Waters wrote: >> We should set the -permissive- flag for the Microsoft Visual C compiler, as >> was requested by the now backed out >> [JDK-8241499](https://bugs.openjdk.org/browse/JDK-8241499). Doing so makes >> the Visual C compiler much less acceptin