Parameter reflection: parameters with "" as their name

[Eric McCorkle]

On 01/24/13 16:53, Alex Buckley wrote:

>> The reflection API doesn't say how it deals with broken restrictions.
>> For instance,
>> - does it supplement missing arguments, as if they have no names
>> - does it silently ignore extra names, or does it report all names
>> present.
>> - if you define any restrictions on the content of names, how does the
>> API deal with broken names
>>    (e.g. does it remove none printable characters (e.g. backspace)).
> 
> To be precise, if there is a mismatch between parameters_count and the
> number of parameters in method_info.descriptor_index (see 8misc.pdf
> 2.1), or if names are not well-formed parameter names, then core
> reflection should throw a ReflectiveOperationException.
> 
> Eric, what does the Reference Implementation currently do? (Remember
> this is not a GPL'd list.)
> 

The reference implementation (which is under active testing and fixing)
presently reports whatever is in the MethodParameters attribute, and
will not throw an exception; however, this is going to change very soon.

The case outlined above is one of the cases I have flagged for testing.