Lucifers, I’d like to discuss how to handle the case when a Perl class defines a method with the same name as a Clownfish method that is excluded from the bindings (manually or because the return type or parameters can’t be mapped). The current code throws an exception. This might be confusing if a user defines such a method in a subclass without even knowing that the same name is used by Clownfish under the hood.
I think the better approach would be to let Clownfish simply ignore such methods. They would work only in Perl-space and never be called from Clownfish. Since they’re not part of the Perl API, this shouldn’t cause problems. What do you think? Nick
