invokedynamic and error messages
Jochen Theodorou
blackdrag at gmx.org
Fri Jan 6 12:18:18 PST 2012
Am 06.01.2012 17:22, schrieb John Rose:
> On Jan 6, 2012, at 4:57 AM, Jochen Theodorou wrote:
>
>> I see where it comes from, but "reusing" that instead of making a new if
>> is not really needed, is it?
>>
>> Do people here agree this should be improved?
>
> The javadoc for this throw is:
> * @throws IllegalArgumentException if the target does not have a
> * leading parameter type that is a reference type
>
> Therefore, I suppose the message could be, "The target does not have a
> leading parameter type that is a reference type".
>
> The current message is supposed to be an abbreviation of that sentence.
> Perhaps it is excessively optimized for space.
I think the current message is shortened a bit too much, this one would
have helped much more. If space is such a big requirement, then it can
stay as it is of course. Regardless the unclear message I found the
reason quite fast ;)
Which reminds me of a question though... why am I not allowed to use
bindTo to bind a primitive?
bye Jochen
--
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org
More information about the mlvm-dev
mailing list