RFR (M): 8135250: Replace custom check/range functionality with check index/range methods in java.util.Arrays
paul.sandoz at oracle.com
Thu Jan 7 08:27:33 UTC 2016
> On 7 Jan 2016, at 09:15, Paul Sandoz <Paul.Sandoz at oracle.com> wrote:
> Hi Kishor,
> Looks good to me. A small but nice improvement.
> I guess you are ok with these throwing IndexOutOfBounds rather than ArrayIndexOutOfBounds.
Actually i just realised you are reusing issue JDK-8135250, which is logged to track a wider range of identified areas in the JDK. Would it be possible to create a new issue [*] related to JDK-8135250 just for the crypto stuff.
[*] If you don’t have the "power ups” to do that i can create one for you.
> Note that i am going to revisit the exception message reporting and with nudging by John the BiFunction to ensure no bounds information is lost. It should not affect this code, but should produce better error messages, and after it might be an opportunity to revisit if you want these to throw ArrayIndexOutOfBounds.
>> On 7 Jan 2016, at 01:18, Kharbas, Kishor <kishor.kharbas at intel.com> wrote:
>> Hello all,
>> Requesting the community to review a patch which replaces custom bound checking functionality with calls to methods in java.util.Objects.
>> The methods affected are CounterMode.crypt() and AESCrypt.encryptBlock(), AESCrypt.decryptBlock()
>> Bug id:
>> Kishor Kharbas
More information about the core-libs-dev