15931 2007-11-10 03:41:09 -0800 Eliminate Instance::createBindingForLanguageInstance() 2011-09-06 23:09:40 -0700 1 1 1 Unclassified WebKit WebCore JavaScript 528+ (Nightly build) All All NEW P2 Normal --- 1 alp webkit-unassigned barraclough ggaren michael.goddard oldest_to_newest 60821 0 alp 2007-11-10 03:41:09 -0800 Instance::createBindingForLanguageInstance() and Instance::createRuntimeObject() currently hard-code all possible binding types in a large switch statement. This is a bottleneck for increasing the modularity of JavaScriptCore. It can be fixed fairly easily but its many callers throughout JavaScriptCore, WebCore and WebKit will need to be refactored to accommodate the change. The fix will probably involve getting callers to instantiate the object wrapper directly instead of calling this utility function. 64901 1 michael.goddard 2007-12-20 18:05:27 -0800 Hmm.. I'd like to see the ability to use Object.prototype functions (like hasOwnProperty etc) on runtime objects (in particular Qt ones).. either RuntimeObjectImp inherits from Object, or certain functions are copied over, or different language bindings could have different runtime JSObjects.. If the callers have to instantiate the object wrappers directly, this would be a bit more difficult than having a centralized convenience function. I don't like having the Instance API itself (the non static functions) exposed, however, since I don't think they add value.