This content has been marked as final.
Show 3 replies
-
1. Re: Warning for potential parameter matching issues
dmlloyd May 28, 2009 11:02 AM (in response to jaikiran)Maybe an error would be a better idea - that way Hudson would catch this well before a release?
-
2. Re: Warning for potential parameter matching issues
jaikiran May 28, 2009 11:24 AM (in response to jaikiran)"david.lloyd@jboss.com" wrote:
Maybe an error would be a better idea - that way Hudson would catch this well before a release?
I thought about the error option too. But i guess it would break backward compatibility. Assuming we need backward compatibility for this :) -
3. Re: Warning for potential parameter matching issues
alesj May 28, 2009 4:38 PM (in response to jaikiran)If we're about to check all possible matches due to missing info,
I would then suggest we use a better mechanism/structure as just plain iteration + matching.
What that exactly is one would need to check some theory,
but this is what I would like at the end:MatchingMechanism m = ...; CtorInfo ctor = m.findCtor(paramTypes, failIfNoMatch, failIfMultiple);
Where this would account for everything, e.g. possible progression, ...