Should I contribute a C++11 RAII wrapper for MTBL objects? about mtbl HOT 4 CLOSED

Hm, in general I'm a fan of keeping library binding separate from the library itself, so e.g., mtbl (containing the C library) and pymtbl (containing the Python bindings for the C library) are kept in separate repositories. So I'd recommend to put this in its own repository. (We don't do much if any C++ work here, so I doubt this is something we'd want to maintain under the farsightsec GitHub org.)

If you're interested in maintaining it in your own repo, I'd be happy to add a section for links to bindings in the README.md file, though!

from mtbl.

(Obviously, I would lose the dependency on boost::noncopyable.)

from mtbl.

Don't read the above code too closely -- it has seen many changes.

from mtbl.

Thanks for the reply! I made the wrapper a lot shorter -- presently, it's 76 lines (plus 30 lines of unit test). It's no biggie to put it in a separate repo, though. I'll comment here when I've put it up, and would be grateful if you mention it in the README.md.

from mtbl.