paurkedal/bdwgc — comment on commit 9d07ead2d0bc217a3ded434372952f7a8db6c17a
File:  line 0
By paurkedal:

Hi Ivan,

On 2012-01-13, Ivan Maidanski wrote:
> The latter seems to me not logically correct as the object is marked (somehow - it is implementation-dependent).

My take on it is that GC_set_mark_bit and GC_clear_mark_bit does not
change the object as seen from the users. Rather they change the
collectors idea about its reachability, which is dependent on an
external link to the object, rather than the content of the object. The
way I use it myself, objects are never changed once constructed, except
possibly for an internal next-link.

> I've committed this patch (adding const to GC_is_marked).

Thanks, I don't mind the others being non-const. I only call this from
low-level allocation and clean-up code, which already contain uintmax_t
to void * casts.

Petter