On Tue, 8 Oct 2002, Andrew Francis wrote:

> I don't actually think they're too bad :P But if the interface were to be
> done from scratch, I would favor something like the below.
> s/malloc/curl_malloc/, if curl_malloc is still on the table.

I've not seen a good motive to add curl_malloc() yet.

> - user chooses whether to allocate memory themselves, or let curl_base64_*
> do it for them
>
> - the functions are expected to do error checking (make sure there's enough
> space to store the output, ensure that input to base64_decode is valid
> base64, etc).
>
> I'll go ahead and implement these sometime this week if you like the idea.

I like the idea. I haven't really thought about the API properly yet though,
but we can always add it your way and if somone come up with a better idea
within short we can adjust to that or remain as you suggest for the rest of
our lives! ;-)

-- 
 Daniel Stenberg -- curl related mails on curl related mailing lists please
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf