Comment #9 on issue 264 by dachev: Allow __noSuchMethod__ implementations http://code.google.com/p/v8/issues/detail?id=264
Chris, I completely understand your compatibility concerns but I think it is not very likely this will break anyone's (browser) code except maybe in a few cases where a long list of circumstances are at place. I'm sure the team is also concerned about maintenance as there are no truly "free" features. However, in my (modest) experience with V8 it seems that the code is designed very well and allows for a single-point, low-maintenance implementation which can be kept in check with unit testing and minimal (if any) coding effort. I think __noSuchMethod__ will be most compelling for server-side JS developers. In this realm V8 enjoys immense popularity. I guess what I'm getting at is that V8 is not just Chrome's JS engine. The community loves it and projects that have started to embed abound. Writing this comment, I truly believe that __noSuchMethod__ is not just one of those "cool" language features you can brag about while talking to other developers but end up rarely used in practice. Its utility was proven on a large scale by Ruby's Active Record and might turn out to be what server-side JS needs to finally take off. In light of the above two paragraphs if the team still doesn't feel comfortable with __noSuchMethod__ in Chrome we can allow it per run-time or compile-time configuration for the people that embed. Given some direction, it would be an honor for me to implement a proper patch. Best regards, Blago -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
