On: Why should I have written ZeroMQ in C, not C++

[evincarofautumn]

Typically what I do in that situation is lightly wrap the API. For instance:

    Image* image = allocate_image(…);
    …
    deallocate_image(image);

    ↓

    struct ImageDeleter {
        void operator()(void* image) const {
            deallocate_image(image);
        }
    };

    unique_ptr<Image, ImageDeleter> image(allocate_image(…));

That certainly can’t work everywhere, but I have yet to be failed by it.

[jmq → evincarofautumn]

You can reduce verbosity of the code by passing destructor function directly to unique_ptr constructor:

    std::unique_ptr<Image, void (*)(Image *)>(image, deallocate_image);

[evincarofautumn → jmq]

Cool, thanks for the tip. I meant to offer an example for the general case.

[jongraehl → evincarofautumn]

People who don't do this are just asking for it.

[malkia → jongraehl]

That's a lot of boilerplate code. Okay there are macros to wrap such things, but I guess it's things like this that would make the future reader of the code puzzled.

[cbsmith → malkia]

jmq & basman provide examples of how to do it succinctly.

[basman → evincarofautumn]

Or, perhaps easier:

scoped_ptr<Image> image(allocate_image(...));