> While the PMC structures themselves don't move (no real need--there of > fixed size so you can't fragment your allocation pool, though it makes Sorry can you expand on this. I don't see the relation between the data being fixed size and the memory not becomming fragmented. > generational collection easier to some extent) the data pointed to by the > PMC can. That's the bit that moves. > > Dan > Well one of the reasons of moving the data is so you can use a trivial stack like allocator. If you don't move the PMC you won't be able to. Benoit
- Rules for memory allocation and pointing Dan Sugalski
- BIGNUM memory and questions (was Re: Rules for memo... Uri Guttman
- Re: BIGNUM memory and questions (was Re: Rules ... Dan Sugalski
- Re: Rules for memory allocation and pointing Michael L Maraist
- Re: Rules for memory allocation and pointing Dan Sugalski
- Re: Rules for memory allocation and pointing Benoit Cerrina
- Re: Rules for memory allocation and pointing Dan Sugalski
- Re: Rules for memory allocation and pointin... Benoit Cerrina
- Re: Rules for memory allocation and poi... Dan Sugalski
- Re: Rules for memory allocation an... Benoit Cerrina
- Re: Rules for memory allocation and poi... Michael L Maraist
- Re: Rules for memory allocation an... Benoit Cerrina
- Re: Rules for memory allocation and pointin... Michael L Maraist
- RE: Rules for memory allocation and poi... Brent Dax
- RE: Rules for memory allocation an... Dan Sugalski
- RE: Rules for memory allocatio... Michael Maraist
- Re: Rules for memory allocatio... Benoit Cerrina