Simon Glover <[EMAIL PROTECTED]> wrote: > 1) When we resize a Resizable*Array (where * = Integer, Float or String) > by calling set_integer_native, we also set the PMC's active_destroy > flag. However, we don't do this when resizing a ResizablePMCArray > (which also has a different memory allocation strategy). Is this > because we don't strictly need to, or is this just an oversight?
Just an oversight as well as in FixedPMCArray. > 2) Why does the ResizablePMCArray PMC use a different memory allocation > strategy, i.e. what advantage does it have over the strategy used by the > other Resizable arrays? Just doubling the allocation size isn't a really good strategy beyond some big size. So I've implemented a IMHO better strategy in the PMCArray. Additionally the helper structure Size*Data isn't really needed. > Simon leo
