#41 Wrong method resolved as argument does not carry the "strict" semantics anymore after convFromRexx()
It turns out that primitive value arguments that are turned into instances of their Wrapper classes as a result of boxing or invoking strict versions of the BSF4ooRexx methods lose their "strict" semantics. As a result when resolving methods dynamically at runtime it may be the case that sometimes the semantically wrong method gets picked.
E.g. the fxml_99 sample when deleting persons in Java 9 or higher might not take effect because the semantically wrong 'remove' method gets picked.
Thinking of this situation it may be the case that there is a need for non-Wrapper objects to gain a 'strict' meaning to force the reflection mechanism to pick a specific method in the case that more than one signature my apply. Ideally it should be solved such, that the current infrastructure can be used for it.
Fixed with [r629].
Related
Commit: [r629]