I'd like to propose the following change to libconcord's API. If it sounds good, I'll be happy to implement it. I'd probably implement this Tuesday night (or maybe Monday). Let me know when is best to avoid any CVS conflicts, since the diff would touch quite a few files.
1) Ensure all libconcord.h APIs either take in (or send back) a length parameter for all buffers read or created. Most do, a couple don't. 2) Pass buffer size into GetTag, so it doesn't assume the input is null-terminated. (There's definitely at least one bug in GetTag right now...) 3) Update the various pieces of code that create buffers not to over-allocate them by 1 byte and null-terminate. 4) Add a function to free buffers, so non-C++ clients can effectively call delete[] through the libconcord API for the buffers they got back. Comments? Thanks. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
