AFAIU, we have pinned VTables for initial version of unloading support. This means that we can still rely that VTable will not change and we can compare it with already known constant. No performance degradation, no new inter-component contracts. -- Ivan
On 10/26/06, Mikhail Fursov <[EMAIL PROTECTED]> wrote:
On 10/26/06, Pavel Pervov <[EMAIL PROTECTED]> wrote: > > Mikhail, > > Now if you introduce one more level of indirection and start comparing > Classes, not VTables, you do not need to enumerate. Yes. But I see 2 cons here 1) Performance: extra memory access for every devirtualization guard. 2) What component will be responsible for this extra level? This is a new inter-component contract.
