Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] [PATCH][UPDATE] ptvcursor : one step further?

From: Richard van der Hoff <richardv@xxxxxxxxxxxxx>
Date: Mon, 12 Mar 2007 11:21:37 +0000
Sebastien Tandel wrote:
I've taking a look at emem.c and it clearly doesn't attach information
about the chunk of memory being allocated. Then ep_realloc may only be
the "allocate new, copy" solution.
Without that information, how do you know how much to copy (if you don't pass the old size explicitly, which would give it a different API from other realloc routines)?

Arf ... I guess we're going to stay without ep_realloc :)

My other concern with building it into the API would be that it might make people think that they could build up a big memory block by extending one byte at a time, without realising that this would have a massive memory footprint.

You're better off without it IMHO.