Re: [zeromq-dev] libzmq v4.0.5

2014-09-26 Thread Pieter Hintjens
I'm going to cut this thread down and reply minimally: And since you asked for it let me complain about this here. :) Maybe http://api.zeromq.org/4-1:zmq-sendmsg could be removed from the table of contents (or moved to a deprecated section in the table of contents so it remains for

Re: [zeromq-dev] libzmq v4.0.5

2014-09-26 Thread Pieter Hintjens
On Fri, Sep 26, 2014 at 4:01 AM, Goswin von Brederlow goswin-...@web.de wrote: And czmq has more of an OO design. So every data object has a send function. One isn't preferable over the other. They are all ment to coexist. Sorry, just want to take this point. You triggered some PTSD now. The

Re: [zeromq-dev] libzmq v4.0.5

2014-09-26 Thread Brian Knox
You can't just open a socket and get to work anymore. I just wanted to say that I find this statement to be empirically false. I just open a socket and get to work all the time. I think this thread is getting fuzzy, and I don't know what the problem is that it is trying to address anymore. On

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Pieter Hintjens
On Thu, Sep 25, 2014 at 4:22 AM, Goswin von Brederlow goswin-...@web.de wrote: Well, and a third time now. Both the now blocks and changed monitor events are API changes that breaks existing stuff. One could even say the ABI hasn't changed, only the API. The changes to the monitor API broke

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Goswin von Brederlow
On Thu, Sep 25, 2014 at 09:00:28AM +0200, Pieter Hintjens wrote: On Thu, Sep 25, 2014 at 4:22 AM, Goswin von Brederlow goswin-...@web.de wrote: Well, and a third time now. Both the now blocks and changed monitor events are API changes that breaks existing stuff. One could even say the

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Pieter Hintjens
On Thu, Sep 25, 2014 at 1:39 PM, Goswin von Brederlow goswin-...@web.de wrote: That is fine for major changes where a completly new function makes sense. But not for minor behaviour changes that only conern corner cases. It doesn't make sense to end up with 20 zmq_sock() like functions that

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Tim Crowder
development list Subject: Re: [zeromq-dev] libzmq v4.0.5 On Thu, Sep 25, 2014 at 1:39 PM, Goswin von Brederlow goswin-...@web.de wrote: That is fine for major changes where a completly new function makes sense. But not for minor behaviour changes that only conern corner cases. It doesn't make sense

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Pieter Hintjens
! .timrc From: zeromq-dev-boun...@lists.zeromq.org [zeromq-dev-boun...@lists.zeromq.org] on behalf of Pieter Hintjens [p...@imatix.com] Sent: Thursday, September 25, 2014 5:20 AM To: ZeroMQ development list Subject: Re: [zeromq-dev] libzmq v4.0.5

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Brian Knox
! .timrc From: zeromq-dev-boun...@lists.zeromq.org [ zeromq-dev-boun...@lists.zeromq.org] on behalf of Pieter Hintjens [ p...@imatix.com] Sent: Thursday, September 25, 2014 5:20 AM To: ZeroMQ development list Subject: Re: [zeromq-dev] libzmq v4.0.5

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Tim Crowder
Subject: Re: [zeromq-dev] libzmq v4.0.5 The surface API remains simple enough, as we deprecate older calls and remove them from examples and so on. The man pages are quite explicit about marking deprecated API calls. We can be more brutal about removing deprecated code, though I've not seen anyone

Re: [zeromq-dev] libzmq v4.0.5

2014-09-25 Thread Goswin von Brederlow
On Thu, Sep 25, 2014 at 02:20:07PM +0200, Pieter Hintjens wrote: On Thu, Sep 25, 2014 at 1:39 PM, Goswin von Brederlow goswin-...@web.de wrote: That is fine for major changes where a completly new function makes sense. But not for minor behaviour changes that only conern corner cases.

Re: [zeromq-dev] libzmq v4.0.5

2014-09-24 Thread Goswin von Brederlow
On Mon, Sep 22, 2014 at 12:13:48AM +0200, Pieter Hintjens wrote: Hi all, This is a pre-release announcement, to give time for backporting. If there are any fixes on libzmq master that you'd like to see in 4.0.5, please let us know. For info, this is what's currently in that release: *

Re: [zeromq-dev] libzmq v4.0.5

2014-09-24 Thread Pieter Hintjens
No, we cannot and will not break existing public APIs. Please read the C4 if you're not clear on this. Bumping the ABI version does not excuse criminal behavior. We can at any point add new classes, and new methods. This is what CZMQ is experimenting with. These classes can move into libzmq if

Re: [zeromq-dev] libzmq v4.0.5

2014-09-24 Thread Pieter Hintjens
Sorry for using the word criminal. I meant, just, that this would be a contract violation. Since ZeroMQ v3.2, we've held to the principle that new functionality may not break existing apps. We broke this rule once or twice afaik. On Wed, Sep 24, 2014 at 12:07 PM, Pieter Hintjens p...@imatix.com

Re: [zeromq-dev] libzmq v4.0.5

2014-09-24 Thread Steven McCoy
Fair warning I am not in a position to push 4.0.5 Windows packages when the release is official. I'm currently on an OSX macbook without any Windows or MSVC toolsets \:D/ -- Steve-o On 21 September 2014 18:13, Pieter Hintjens p...@imatix.com wrote: Hi all, This is a pre-release

Re: [zeromq-dev] libzmq v4.0.5

2014-09-24 Thread Pieter Hintjens
OK, no particular hurry. Perhaps there's someone here who can host this? On Wed, Sep 24, 2014 at 9:25 PM, Steven McCoy steven.mc...@miru.hk wrote: Fair warning I am not in a position to push 4.0.5 Windows packages when the release is official. I'm currently on an OSX macbook without any

Re: [zeromq-dev] libzmq v4.0.5

2014-09-24 Thread Goswin von Brederlow
On Wed, Sep 24, 2014 at 05:46:14PM +0200, Pieter Hintjens wrote: Sorry for using the word criminal. I meant, just, that this would be a contract violation. Since ZeroMQ v3.2, we've held to the principle that new functionality may not break existing apps. We broke this rule once or twice afaik.

[zeromq-dev] libzmq v4.0.5

2014-09-21 Thread Pieter Hintjens
Hi all, This is a pre-release announcement, to give time for backporting. If there are any fixes on libzmq master that you'd like to see in 4.0.5, please let us know. For info, this is what's currently in that release: * Fixed #1191; CURVE mechanism does not verify short term nonces. * Fixed