[nanomsg] Re: Status

  • From: Martin Sustrik <sustrik@xxxxxxxxxx>
  • To: nanomsg@xxxxxxxxxxxxx
  • Date: Fri, 28 Feb 2014 14:30:40 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28/02/14 14:18, Dirkjan Ochtman wrote:

>> #199 should fix hangup on windows, so it's pretty important
> 
> Should... Have you tested it? Do you have a Windows box to test
> stuff on?

I believe Paul has access to our Window server so he presumably have
checked it there. Still, it would be nice to have buildbot running on
the server so that all the commits are automatically tested on Windows.

>> #200 will break bindings so we should think twice, but from the
>> other side, earlier we'll make breaking changes is better.
> 
> I think we should take it. Maybe it would be nice to expand the
> commit message a little bit with a short description of what you've
> added and why it's useful?

The alternative is to simply add nn_symbol2(...) function. That would
leave the existing bindings working and would allow new ones to get
extended info. The function is not part of the core API (sockets) and
thus the little mess won't hurt that much.

Martin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTEI+AAAoJENTpVjxCNN9Y63IH/2vHYzeGdzsvkXs8ETnZZ+fe
avL6N5EL4iOsQmO6ZYCpBwYUlL4tBFOXC40HIjnkXcP5JCnMdn6H4riaEKM3l3r1
8lmlw8A7dxbtw1ZfXESg83E00wiybXjHo7FMoSHR3vne4GbAWxfJ/4NbgVWtVOPi
Lp1IaRX2Y813tPBwDr+wHqZhWJbGRd0CVB2YgpfsQu+Sm87bde3q3GhLboEAAkDu
W+1RzouP27z1FRIB3Hu9ws0wbo+XaRD0kMWSl8agG3MSnczh2GelAKnRwPKuQxn4
V4nITEFrXSFKSlTBaLtk9aOByHTuuwIpRNZU8k30pVMvfaNN2G6lNvh1UNyf6uM=
=3ax+
-----END PGP SIGNATURE-----

Other related posts: