create/destroy name change proposal

[Jason Kraftcheck]

Mark Beall wrote:
> Mark,
> 
> I didn't say that I think iMesh_destroyMesh SHOULD free memory, I just
> said that could be a reasonable requirement. That could be a problem for
> an implementation that uses a true garbage collecting memory manager
> (although one can usually force them to do their garbage collecting), it
> also assumes that implementations are written in a language that allows
> you to explicitly control memory management (which, practically, may be
> a reasonable assumption).
> 

Also, what does everyone mean by "free" memory?  Return it to the pool of
memory used by malloc?  Return it to the system?  Most malloc/free
implementations will not do the latter.  What happens if an implementation
has its own memory management implementation that doesn't go through
malloc/free and the "deleted" memory is not composed of whole pages?

- jason