Talk:Respond to an unknown method call: Difference between revisions
Talk:Respond to an unknown method call (view source)
Revision as of 16:14, 25 February 2010
, 14 years agoDon't remove, mark incorrect.
(Some contributions are wrong and stupidly so, so will squelch) |
(Don't remove, mark incorrect.) |
||
Line 8:
I see that some languages are putting in how they do errors when you try to do an unknown method. This is wrong! The object must have a chance to respond to a method call (or message) which it doesn't know the name/topic of ahead of time. Throwing an error at compile time is the total antithesis of this. I'm going to go through and remove all the contributions by people who have obviously "not got it". –[[User:Dkf|Donal Fellows]] 15:05, 25 February 2010 (UTC)
: Don't remove, but mark them '''incorrect''', and include your reasoning. If you remove them, there's not much trace of why it was removed, and some editor who comes along and drops in a new example might make the same mistake. If someone fluent in the language then comes along and marks it with the Omit template, then that's that. --[[User:Short Circuit|Michael Mol]] 16:14, 25 February 2010 (UTC)
| |||