From: Perry C. <per...@us...> - 2002-05-01 20:58:46
|
It's possible that the allocators would allocate space depending on the class type (e.g. BIBOPS) so I am not sure it would be general enough. On the other hand, good software engineering would argue for abstracting it now and perhaps enrichnig the interface later if and when we write such a collector. So I give it a tentative ok. Perry David P Grove/Watson/IBM@IB...@ww... on 05/01/2002 09:13:00 AM Please respond to jik...@ww... Sent by: jik...@ww... To: jik...@ww... cc: Subject: [Jikesrvm-core] proposed change to VM_Allocator "interface" Observation: the code for allocateScalar, allocateArray, cloneScalar, and cloneArray is pretty much identical in all versions of VM_Allocator. I'd like to move this code into VM_Runtime.XXX VM_Allocator would then export a single function getHeapSpaceFast(size) that would be called by the allocation routines in VM_Runtime. Any objections? --dave _______________________________________________ Jikesrvm-core mailing list Jik...@ww... http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jikesrvm-core |
From: David P G. <gr...@us...> - 2002-05-01 21:14:31
|
good point. I'll define it as getHeapSpaceFast(size, tib) and then an allocator that wanted to do BIPOP could do that without changing the interface. --dave |