On 2007.11.26., at 13:36, Attila Szegedi wrote:
> On 2007.11.25., at 2:59, Charles Oliver Nutter wrote: > >> Notes as I work through the implementation. >> >> * I know we talked about this at one point, but it would fit better >> with >> JSR292 and even current hotspot optimizations if the MOP provided a >> way >> to invoke by querying for method objects. So rather than >> >> Object call(Object target, Object id, CallProtocol protocol, Map >> args) >> >> You'd have >> >> Callable query(Object id, Map args) (args for signature selection >> where >> appropriate) I assume this'd actually be: query(Object thisObject, Object callableId, Map args) query(Object thisObject, Object callableId, Object... args) My question however is: what exactly is the invariant that we want to optimize for here? - type of thisObject - types of arguments Also, based on your current experience, is it acceptable to return a callable that runs fast for the type(s) it is optimized for, but is also able to run when passed types it is not optimized for, or should it fail when passed unexpected types? Attila. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
