tag:blogger.com,1999:blog-20975090.post8876331873631027858..comments2026-02-05T05:43:08.642-06:00Charles Oliver Nutterhttp://www.blogger.com/profile/06400331959739924670noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-20975090.post-4222049463756241762007-07-12T07:52:00.000-05:002007-07-12T07:52:00.000-05:00In Mono's JScript.NET implementation we annotated methods of the run time with [JSFunctionAttribute(HasThisObject | HasEngine | HasVarArgs)] and so on. The compiler would have a look at those annotations and only pass information that the target method actually needs.<BR/><BR/>We were also able to directly pass arguments via the stack for methods that take a static number of arguments. <BR/><BR/>Perhaps that could work here as well?flgrhttps://www.blogger.com/profile/05128769452612477118noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-63773894287085058722007-07-11T18:14:00.000-05:002007-07-11T18:14:00.000-05:00Sam: Not sure I understand your first comment, but yes, I'm probably going to handle the metaclass that way in the short term since it eliminates a dup and call. Ultimately I think the best option may be eliminatine that parameter entirely except when it's needed, but I haven't yet determined when I can omit it.Charles Oliver Nutterhttps://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-13038979309907267042007-07-11T17:00:00.000-05:002007-07-11T17:00:00.000-05:00Can you cache the MetaClass and dispatcher for each local variable in another local variable on assignment to reduce that to a single lookup?Samhttps://www.blogger.com/profile/14121705654622595662noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-62317748180945630562007-07-11T16:52:00.000-05:002007-07-11T16:52:00.000-05:00How about replacing with nil on assignment instead of later when it is called?Samhttps://www.blogger.com/profile/14121705654622595662noreply@blogger.com