[John Keiser]
> What reasons can you see to add this sort of extra check? The only
> one I can see is to avoid allowing Joe Schmoe's code to set Class,
> Thread, and reflect.* native state (or, more generally, to avoid
> having two different distributions try to modify the same native
> state pointer). I think people should just write in the docs what
> native state pointers they're using, and that should warn others not
> to set those pointers.
I was not thinking about any extra code, just a textfile to note which
pointers is used to store native state, to avoid using the same
pointer type for different thinks.
Almost like Linux magic number registration.
--
##> Petter Reinholdtsen <## | [EMAIL PROTECTED]
