On Donnerstag, April 3, 2003, at 07:57 Uhr, Dalibor Topic wrote:
The way I understand that is that gilgul operates on single instances, while HotSwap operates on all, right? So Gilgul could be extended to apply to all instances if there is some way to enumerate all instances.
Yes, modulo atomicity of course. But I there are easy ways in kaffe to keep the world from executing, right?
How do HotSwap and Gilgul affect subclasses? If I replaced an/all java.io.Reader instances with java.io.MyOwnReader, shouldn't that affect BufferedReader instances as well, changing their object hierarchies?
Hmm, I haven't thought about that before, but my gut feeling is that this should indeed affect the inheritance hierarchy. However, we should need to think about the consequences in detail.
Maybe a combination of Gilgul and Guarana could be useful in order to replace metaobjects at runtime?!?
Alexandre, what do you think?
The Gilgul compiler is based on the original Java compiler by Sun. I don't know the reason why it doesn't work on kaffe - I guess there are some libraries missing. This wasn't important to us yet.
O.K. That explains the licensing, too ;)
Yep - I know it's annoying... :}
But in fact it should be quite easy to modify other Java compilers in order to include the Gilgul constructs as well. The really interesting parts are happening in the VM...
Pascal
P.S.: I am away for a conference for the coming week, so I am probably to respond in a timely fashion.
_______________________________________________ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
