If memory serves me right, Erik Bågfors wrote: > But if I write a library in ruby that depends on the missing_method > method it will not be usable from other languages, since those languages > doesn't call missing_method if the method they try to call doesn't > exist.
Hmm... that's twisting language features with virtual machine instructions. Actually that's a gray area as far as I can see ... we'll have to go on with `n' number of methods for `n' languages for member resolution ... > Of course, in real life I don't think that's a problem because I haven't > seen much use of missing_method. Unfortunately I use a lot of __getattr__ for my python code (especially GUI) ... > Also, having a instruction would be faster which of course is more fun > :) Yes... But this not only makes it ugly (as an instruction) , but slow as well ? . Like you said only a small number of people use this feature , does it make sense to slow down the rest ? . And how does hacker ZZ add a new language with a different member lookup without getting his patches inside Parrot ?.. Anyway I'm not *against* implementing this , I'm just questioning the *need* to implement this ... Just a question for the philosophers ... Gopal -- The difference between insanity and genius is measured by success
