[zeromq-dev] what happens to the bindings with libzmq libzapi ...

Martin Lucina mato at kotelna.sk
Tue Apr 26 13:04:11 CEST 2011


ellisonbg at gmail.com said:
> I know this is the plan, but I don't think it makes any sense to have
> two different C APIs and two different C++ APIs like this.  I think it
> will be confusing to users and make the development workflow difficult
> (which API do I fix that bug in?  which API do I add such and such
> feature to).  This also makes the jobs of language bindings more
> difficult as well (which should we wrap?).

+1

> For a project written in C++, that C++ API, should be *the* C++ API
> and the C API should be a thin layer on top of that.  If those APIs
> are broken or confusing, let's just fix them in 3.0.

The C++ API was always implemented as a simple wrapper over the C API (see
zmq.hpp). Now, I believe that there are some people who want more
functionality in the C++ API than there is provided by what is in the core;
hence splitting it off into it's own project (which essentially just
consists of the zmq.hpp and a manual page) would make sense.


> I haven't followed the development closely enough, but I just buy
> this.  Groups have developed software that is much more complex that
> zeromq with C/C++ APIs and not had any difficulty or needed to develop
> additional APIs.  What exactly is not scalable?

Martin Sustrik is not scalable :-) Hence the splitting off of various
functionality from the core.

> > So, issue 188 is in libzmq, not in libzapi. We need to fix it in
> > libzmq master, then downstream that fix to 2.1 so that it will be
> > available to the language bindings.
> 
> This is exactly the confusion that I am predicting will annoy all of
> us forever if we allow this to continue....

+1

-mato



More information about the zeromq-dev mailing list