Hi,
Is it possible to implement two interfaces in one object?
On Thu, Jun 10, 2010 at 4:29 PM, Knut Olav Bøhmer bohmer@gmail.com wrote:
Hi,
Is it possible to implement two interfaces in one object?
java.lang.reflect.Proxy surely allows it. Whether this is supported by abcl or not is another matter. I will investigate.
Alessio
2010/6/10 Alessio Stalla alessiostalla@gmail.com:
On Thu, Jun 10, 2010 at 4:29 PM, Knut Olav Bøhmer bohmer@gmail.com wrote:
Hi,
Is it possible to implement two interfaces in one object?
java.lang.reflect.Proxy surely allows it. Whether this is supported by abcl or not is another matter. I will investigate.
Unfortunately, neither jinterface-implementation nor jmake-proxy currently supports this. It would not be hard to add, however, we probably need to choose one proxy-maker to keep and which one to deprecate/eliminate first. I sponsor jmake-proxy obviously, because I wrote it and because it's more flexible - you can build a proxy out of a hash-table of closures, a package, a function, or even a user-defined object if you want, and you have the option to provide a "lisp-this" object to dispatch on, as initially suggested by Ville. Also, jmake-proxy is currently used by the jsr-223 stuff to implement the getInterface() method. But, I'm open to other opinions of course.
Alessio
On 11 June 2010 00:16, Alessio Stalla alessiostalla@gmail.com wrote:
java.lang.reflect.Proxy surely allows it. Whether this is supported by abcl or not is another matter. I will investigate.
Unfortunately, neither jinterface-implementation nor jmake-proxy currently supports this. It would not be hard to add, however, we probably need to choose one proxy-maker to keep and which one to deprecate/eliminate first. I sponsor jmake-proxy obviously, because I
Add the capability to jmake-proxy and write a comment for jinterface-implementation that it's semi-deprecated and people are advised to use jmake-proxy. Let's not eliminate it yet.
Just my 0.02.
armedbear-devel@common-lisp.net