RFR: 8253176: Signature.getParameters should specify that it can throw UnsupportedOperationException [v2]

[Xue-Lei Andrew Fan]

On Thu, 28 Apr 2022 04:41:20 GMT, Xue-Lei Andrew Fan <xuelei at openjdk.org> wrote:

>> Besides this Signature-specific condition, there is the common condition where provider cannot (or do not) generate default parameter values. {@code null} is used as the catch-all result, but as you said, describe various conditions tersely and correctly is key.
>
>> > What does it refer to with 'it'? Is 'it' refer to the implementation generated parameter values?
>> 
>> 'It' refers to the parameters containing all of the parameter values including the supplied ones and provider-generated ones if any.
> 
> The full sentence is, "If the required parameters were not supplied and the underlying signature implementation can generate the parameter values, it will be returned."   As there is no supplied value, I think 'it' refer to the provider-generated ones if any.  As the previous noun is "the parameters values", I'm not sure if the use of 'it' here is properly.

> Can you clarify what is the A and B that you are referring to?

The sentence is, “If the required parameters were not supplied and the underlying signature implementation can generate the parameter values, it will be returned. Otherwise, {https://github.com/code null} is returned."

I read "the required parameters were not supplied" as condition A; and "the underlying signature implementation can generate the parameter values" as condition B.

-------------

PR: https://git.openjdk.java.net/jdk/pull/8396