|
> > The heap instructions were not a dead end. It all worked. Why will the > over allocation method not work for you ? Will not the programmers have to > call the allocate and deallocate functions that call down to the mi heap > instructions ? Well, I'm thinking that they might do something stupid like: C alloc size myPtr C** add stuff to the allocated storage C eval newPtr = swMemExpand( myPtr: C bytesToInsert: C insertAtOffset) (where swMemExpand() is one of my routines) So if they didn't use my routine to create the initial allocation, the header data would be missing. I really don't want to force use of the service program to be an all or nothing proposition. Ideally, they should be able to freely mix my memory routines with the native stuff. John Taylor
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.