Re: [Beaver-devel] str_replace_tokens

[Michael Terry]

Leslie Polzer wrote:
> I don't know if you did this function, but maybe you can answer my
> question nevertheless. Prototype is:
>
>         gchar *str_replace_tokens (gchar **string, gchar obj,
>                 gchar *replacement)
>
> Why's string a gchar** and not just a simple gchar* ? I don't see
> any sensible reason for it, it's always referred to as *string anyway.

Yeah, I am responsible.

The reason is so that I can write
str_replace_tokens (&str, 'l', "hi");

instead of
str = str_replace_tokens (str, 'l', "hi");

That's all, to my knowledge.  Since the function actually realloc's the 
string, you would never assign the return to anything but the same pointer.

Of course, then the question is why realloc instead of malloc.  I knew 
how I was going to use the function, and I knew that it would be simpler 
for me if I realloc'ed (because otherwise I would have to free the old 
string, which I never care about anyway).

Feel free to change it.

-mt

pgpza6gsI8Iip.pgp
Description: PGP signature