On 21 Jul 2006, at 15:24, Phil M wrote:
On Jul 21, 2006, at 9:44 AM, Theodore H. Smith wrote:
It seems I have a memory leak somewhere and I just have to find
it. I disabled the picture so my return value is NULL, and the
leak continued to occur so it is something with my code.
REALpicture Function() {
REALpicture bla = REALnewPicture(a,b,c);
return bla; // this wonn't leak
}
REALpicture Function() {
REALpicture bla = REALnewPicture(a,b,c);
return 0; // this WILL leak
} // because we created "bla", but now nothing can unlock it.
Just so you know.
OK, thanks. I have gotten spoiled with REALbasic memory-
management, my university classes didn't really get into memory-
management and I don't have any of my C/C++ books with me. It
takes me a lot longer than I would like to get this plugin written,
but the results are much better than what I was getting in pure
REALbasic.
I don't think even a University class would go into the interactions
between ref counted and non-refcounted memory management systems :)
You are having to write code that bridges two worlds here... Can be
quite awkward.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
