[Openmcl-devel] memory

Tim Bradshaw tfb at tfeb.org
Mon Apr 12 15:50:13 PDT 2010

On 12 Apr 2010, at 22:32, Gary Byers wrote:

> If you don't need to handle these kinds of cases, then yes, the hard  
> part is
> knowing how to obtain the size of some primitive object.

I agree completely with the text I elided - the difficult bit of this  
kind of thing is walking the structure, dealing with sharing &  
circularities etc.  *However* that is generally code that the user is  
able to write without dependencies on the internals of the  
implementation (and indeed it's code that *only* they can write as it  
depends on their knowledge of what stuff counts for them).  I think  
the sizeof primitive is something reasonably important, because it's  
the bit you *can't* write without understanding the implementation.

More information about the Openmcl-devel mailing list