Dan Sugalski wrote:
*) The vtable split needs to be defined and implemented. I'd like some macros to access the vtable entries themselves, since there may be a number of structural changes and I don't want to have to keep redoing the code every time some element shifts from one spot to another.
http:[EMAIL PROTECTED]/msg14250.html
*) I'd like to get access to pmc elements done via macros as well--I think it's time to split PMCs into pieces, since we're definitely trashing the cache in the common case with things we don't commonly need. (Like the metadata, thread, and GC stuff) PMCs are 40 bytes on my PPC system. Too much cache fluff.Me2. The macro stuff should be easy, it's all in popj.h and most are macros already.
Additionally for such *big* changes in infrastructure it would be a really good thing to have a *microparrot*. Only some PMCs (Hash, Array, Int, Num, String) minimum infra structure, cut down VTABLE for only very basic things.
This would of course not run tests but would be a valuable program to check different deep core changes faster without really big patches to the whole and everything.
leo
