On Sat, 14 Aug 2004 15:36:40 -0700, Keith Rollin <[EMAIL PROTECTED]> wrote: > I'd like to suggest three alterations to this paragraph. > ...
Thanks for setting me straight, Keith. I didn't know those details. As to fixing the article - I don't feel very motivated - I don't maintain this site anymore. And not that it matters greatly, but another advantage of my approach is that you can post-process allocation/deallocation data and analyze memory usage during the lifetime of the program. I have a simple script that dumps this data into csv file where each row is a total memory usage after each allocation/deallocation. I can open this file in Excel and graph the memory usage during program lifetime. Interesting information and sometimes even useful (e.g. if you want to compare the usage for the same codepath before some change to the code and after, to see it's impact on memory usage). It would be great if you guys added such functionality into future versions of simulator. Since all allocations have to go through your code, you could not only do a very accurate memory stats but also use one of the well known techniques for detecting memory overwrites (writes past allocated memory), underwrites (writes before allocated memory), double frees etc. Putting such functionality in simulator would have the maximum benefit for the Palm OS programming community (and indirectly for Palm by increasing the quality of software written for Palm). Krzysztof Kowalczyk | http://blog.kowalczyk.info -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
