On Wed, 27 Jun 2007 16:00:10 -0400 [EMAIL PROTECTED] wrote: >I forgot to say, if want, you could reallocate memory when it >detects buffer too small. > >Other option is to rewrite all those functions to use local >variables, instead of the global. Lots of work to do this. Not >sure worth it? >
After looking at code, best thing to **NOT** do away with GeneralBuffer. (displaybuffer). Reason is there are ~628 calls to load into this buffer. Now we have 1 malloc, and 1 free, so that is tons less malloc/free calls we no have to worry about. In hunt for memory leaks, I know now is not present in those routines that use this. So no more changes to that is best until find other leaks. -- Getting Married? Click for People's top wedding picks http://tagline.hushmail.com/fc/Ioyw6h4emakO3gyVpQtj1YVSMyQSXbPSSDTBuDkPvUkIVQLP1nRsOy/ _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
