Please, take a look at the doxygen documentation. As for evbuffer - you never loose ownership of it, the data usually just gets removed from it. The documentation could be clearer on that.
Niels. On Feb 9, 2008 4:33 AM, Florian Lohoff <[EMAIL PROTECTED]> wrote: > > Hi, > > i was once again reading the manpage and the doxygen documentation on the > webpages but i was really confused on whether e.g. "bufferevent_write_buffer" > takes over ownership of the passed evbuffer. I mean evbuffer_new is the > source of the evbuffers but who is the consumer or sink? > > Its hard to understand from the documentation what the lifecycle of an > evbuffer is within the callbacks, evbuffer and bufferevent API. > > I mean - i find my way by gdb and valgrind - either crash or memleak > shows the misusage of the API but i guess fixing the documentation > would be helpful to a lot of interested partys. > > But anyway - thanks for libevent - great tool i dont want to miss. > > Flo > -- > Florian Lohoff [EMAIL PROTECTED] +49-171-2280134 > Those who would give up a little freedom to get a little > security shall soon have neither - Benjamin Franklin > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFHrZ2cUaz2rXW+gJcRAlkyAJ49RHE5wJbOx1ZOPAH3f0YwyTkRGQCeKsjV > QHaNxQUTddbnGVEJSHscrUQ= > =Sw/z > -----END PGP SIGNATURE----- > > _______________________________________________ > Libevent-users mailing list > Libevent-users@monkey.org > http://monkeymail.org/mailman/listinfo/libevent-users > > _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
