From: Peter C. M. <Pet...@na...> - 2008-05-13 00:30:29
|
I finally gave in and created a branches/v5, since the DynamicArea replacement is much bigger than originally expected. At least initially, I'm probably going to drop a number of things that directly use the DynamicArea implementation (e.g. Serializer/Restorer). Since this is such a big change anyways, I will also change the Instruction interface to execute(ThreadInfo), modify the ElementInfo structure, and therefore call this "version 5" (we have a milestone for this by end of August) PLEASE NOTE - the current v5 only has the direct DynamicArea references replaced by a new "Heap" interface wherever possible, i.e. there are a lot more changes to come, and this should NOT YET be the version to use in GSoC. However, you should refrain from using DynamicArea internals (esp. Area.elements) in your GSoC code. Please let me know if that's a problem, so that I have an idea who is working off branches/v5 instead of trunk. Please also note that I don't want to kick off a flood of branches with this. We don't have enough time & resources to work on lots of different branches simultaneously, and branches eventually have to get merged back. If nothing else, be advised that branching with the current Eclipse/Subclipse has it's pitfalls. -- Peter |