[Pharo-project] Issue 3399 in pharo: SystemNavigation should directly use CompiledMethods instead of their wrapper where its appropriate
Status: Accepted Owner: siguctua Labels: Milestone-1.3 New issue 3399 by siguctua: SystemNavigation should directly use CompiledMethods instead of their wrapper where its appropriate http://code.google.com/p/pharo/issues/detail?id=3399 SystemNavigation exposing the currently running system to tools. This means that it is always operates with objects located in system in its current state, not somewhere outside. In own turn this means, that it should not use any indirections or wrapping real compiled methods with method references, but instead should pass them directly to development tools. For navigating remote systems or any other kinds of indirection, one could create a subclass of SystemNavigation, which then can expose the remote system internal using compiled method references, classes and other proxies like that. This also means that we should analyze and impose the required protocol which both CompiledMethod and MethodReference(s) should comply with. As well as Classes and MetaClasses, Packages and organization.
participants (1)
-
pharoï¼ googlecode.com