Hm. Well, both are a discriminator, then; dispatch to code which
presumes the contents of the union is quite frequently done without
examining the flags.
The flags are *never* consulted for a vtable call in classes/*. DOD does different things if a Buffer or PMC is looked at, but that doesn't matter here.
Then, updating the vtable would atomically update the flags as well.
Doesn't matter.
Or, hell, put the flags directly in the VTABLE if it's not necessary for them to vary across instances.
No, flags are mutable and per PMC *not* per class.
... in the multi-thousand-
line-diff it was, yet. :( Else you'd have the patch already
1) *no* multi-thousands line diffs 2) what is the problem, you like to solve?
Do any PMC classes use *both* struct_val *and* pmc_val concurrently?
E.g. iterator.pmc. UnmanagedStruct uses int_val & pmc_val. This is no problem. These PMCs don't morph.
leo
