Mark Wielaard wrote: > I believe that with your and Andrew's work we are now synced > for the VM Classes between generics and trunk.
Yeah, I think so too. > There is one change to Class.newInstance() from you that > never went in. > I didn't see any objections to it, but also no strong support > for it. Do you still need that one? > http://developer.classpath.org/pipermail/classpath/2006-March/ > 000728.html I currently have a hack in place to replace the Class.newInstance method and while that's a bit ugly it works and I think I'd rather have that hack than some VM specific hook at this point in time, but I may revisit the issue when I'm more confident that the hook is correct and could possibly be appropriate for other VMs as well. > It would be a good point to declare the vm classes interface > frozen for now and work towards a new snapshot release that includes > them. Agreed. > Unfortunately I am going on vacation in about an hour and then attend > LinuxTag the week after so I won't be able to coordinate it. But if > someone else would and could see if the vm interface is doable for > other runtimes (I believe it works with jamvm and cacao already with > only minor patches that add some noops for now) that would be > appreciated. I would hardly call going on vacation "unfortunate" ;-) Prettige vakantie! I don't anticipate any difficulaties for the other VMs, but should they arise, I'm sure we'll work it out ;-) Regards, Jeroen
