OK, my fault. I've fixed that: https://github.com/hintjens/libzmq/commit/ce8fbb26cb864c8e55978a614743d88019aeda4a
On Wed, Jun 25, 2014 at 2:10 AM, Peter Kleiweg <[email protected]> wrote: > Pieter Hintjens schreef op de 24e dag van de zomermaand van het jaar 2014: > >> I've added code to do up-front checking of TCP addresses, so that >> these and other syntax errors get caught immediately: >> https://github.com/zeromq/libzmq/pull/1106 > > I still had to update my test code in Go, because the error > messages returned by 0MQ are different. In 4.0.4 it was > "invalid argument", in 4.1.0 it is "resource temporarily > unavailable". > >> >> On Fri, Jun 20, 2014 at 6:44 PM, Peter Kleiweg <[email protected]> wrote: >> >> >> >> > A socket connect for these two addresses return no error. With >> >> > version 4.0 they both return the error "invalid argument": >> >> > "tcp://localhost:invalid" >> >> > "tcp://in val id:1234" > > > > -- > Peter Kleiweg > http://pkleiweg.home.xs4all.nl/ > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
