All those tips are great for optimizing performance in compiled code running on Pentium machines. Small problem we here are interpreted code. All code is evaluated at run time. Anyway that kind of optimization is to try and snip off milliseconds. Here we are talking about seconds going to waste not 1 millisecond faster or slower. About the other idea of using one set of objects and updating. I like it BUT: * We need some sort of fail-proof content delivery mechanism. * If you want this then you definitely need to restructure the API to provide an Application like interface with mem manegment. 8an _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-dev
- [Dynapi-Dev] Freeing Memory Eytan Heidingsfeld
- RE: [Dynapi-Dev] Freeing Memory Pascal Bestebroer
- Re[2]: [Dynapi-Dev] Freeing Memory Robert Rainwater
- Re: [Dynapi-Dev] Freeing Memory Raymond Smith
- Re: [Dynapi-Dev] Freeing Memory Doug Melvin
- RE: [Dynapi-Dev] Freeing Memory Pascal Bestebroer
- Re: [Dynapi-Dev] Freeing Memory Raymond Smith
- Re: [Dynapi-Dev] Freeing Memory Eytan Heidingsfeld
- Re: [Dynapi-Dev] Freeing Memory Jeff Greenberg
- Re: [Dynapi-Dev] Freeing Memory Raymond Smith
- Re: [Dynapi-Dev] Freeing Memory Doug Melvin
- Re: [Dynapi-Dev] Freeing Memory Raymond Smith
- Re: [Dynapi-Dev] Freeing Memory Doug Melvin
- SV: [Dynapi-Dev] Freeing Memory Bart Bizon
- Re: [Dynapi-Dev] Freeing Memory Doug Melvin
- RE: [Dynapi-Dev] Freeing Memory Pascal
- Re: [Dynapi-Dev] Freeing Memory Raymond Smith
- Re: [Dynapi-Dev] Freeing Memory Jordi - IlMaestro - Ministral
