Re: memory not freed up?

Brooks Moses wrote: 
Rich Townsend wrote:

Can I suggest a much-simpler strategy to avoid memory fragmentation: always try to deallocate arrays in the order in which they were created. As far as I'm concerned, any approach more sophisticated than that will be highly platform-dependent, and therefore may have sub-optimal performance on platforms for which it was not 'tuned'.


My naive impression would be that the appropriate strategy would be to deallocate arrays in the _reverse_ order from the order in which they were created.

Am I missing something obvious, or was this a typo? 

Typo. Too little coffee!

cheers,

Rich
.