> No. It means that the object gains a type header that allows for dynamic > dispatch, RTTI, and such.
@Jehan Thank you for pointing that out! I thought the {.inheritable.} pragma was the solution to my question, but if it adds a "dynamic dispatch" pointer to the object, than I cannot use it. Sounds like it basically does the same thing as "object of RootObj"; my "messages" are going to be passed to other threads, serialized over the network, ... This just won't do. So I guess I'm back to "previous: pointer"