Am Montag, 30. Oktober 2006 22:58 schrieb Kevin Tew: > Using either of those flags ( PObj_private0_FLAG or PObj_private2_FLAG > ) break other tests. > > I'm up for more suggestions.
Sorry for the very delayed answer. Reusing these compile-time flags isn't really safe obviously, as running the code of course might need the reused flags for runtime. I should have thought of that in the first place. Therefore we need: - a new field in the struct Parrot_sub / struct Parrot_coro: UINTVAL comp_flags [1] - it's usable as PMC_sub(pmc)->comp_flags then - all the compile time flags should go there (moving the new one first as a test is of course ok) - the flags can then be defined in sub.h and imcc can just reuse these defines (using the current imcc bits, which are more restricted) leo [1] include/parrot/sub.h please regard the common order of fields in these 2 structs
