I'm as hesitant to implement this as I would be to throw an exception
- if a method receives an argument of a different type than is expected
- if a method receives a different number of arguments than expected
- if an option is set/get that the original plugin author is not aware of
These provides no benefit at run-time, only at development/debug time and all have serious potential to limit extensibility.
Just as an example, declaring it an exception to call a non-existent widget method would preempt someone from creating a noSuchMethod implementation for jQuery UI widgets, something that is currently a real possibility, and perhaps even interesting.
If this is so sorely needed at development/debug time, couldn't it simply be opted in via a debug plugin? Such a debug plugin would be very easy to write if we were to build in a noSuchMethod hook but difficult (if even possible) to write if we declared such a function call an exception.