search for: syncblock

...the use of an extra word for typed nulls. If you look at something like the CLR you will see that you have very fast access to an objects type, after all when you have a reference to an object what you really have is a reference to an objects' object header. From there you can access an objects syncblock (if it has one, which is before the obj header) and the objects' method table which includes the relevant pointers to the objects' type among other things. It simply means you do a few hops, each of which is a constant operation anyway. Maybe I'm missing something key about the languag...

...> word for typed nulls. If you look at something like the CLR you will see > that you have very fast access to an objects type, after all when you have a > reference to an object what you really have is a reference to an objects' > object header. From there you can access an objects syncblock (if it has > one, which is before the obj header) and the objects' method table which > includes the relevant pointers to the objects' type among other things. It > simply means you do a few hops, each of which is a constant operation > anyway. > > Maybe I'm missing so...

On Tuesday 16 June 2009 07:37:32 Talin wrote: > A while back there was a discussion thread about whether an accurate, > concurrent garbage collector could be "generic" in the sense of being > able to support multiple different languages efficiently. After having > done some work on this, I now believe that this is the case - using C++ > policy-based design principles, you

A while back there was a discussion thread about whether an accurate, concurrent garbage collector could be "generic" in the sense of being able to support multiple different languages efficiently. After having done some work on this, I now believe that this is the case - using C++ policy-based design principles, you can create a set of modules that represent different aspects of