|
Scott, > > If you need to mix & match with callers that use the RPG alloc & dealloc > op-codes, though, you're going to have problems no matter what you do :) > And if I don't, I'm just going to have problems of a different sort. :) Imagine someone passing me a pointer that wasn't built using my custom allocation routine, and then (by chance) finding an integer anyway when I peeked behind the curtain for a hidden header that was never created. Oh what fun those results would be to debug! Of course, such a problem can be made a lot less likely to occur by adding some type of UUID to the header section, but even that wouldn't make it bullet proof. I think MI is the only reliable way to do it. Thanks for the suggestion though. John Taylor
This mailing list archive is Copyright 1997-2026 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.