RE: [FORGE] updating sockets

[JohnD]

-----Original Message-----
From: JohnD [mailto:address@hidden 
Sent: Wednesday, December 03, 2014 4:43 PM
To: address@hidden; 'Paul Dreik'
Subject: Re: [FORGE] updating sockets


Date: Wed, 03 Dec 2014 21:05:32 +0100
From: Paul Dreik <address@hidden>
To: Juan Pablo Carbajal <address@hidden>,       Octave Maintainers
        List <address@hidden>
Subject: Re: [FORGE] updating sockets
Message-ID: <address@hidden>
Content-Type: text/plain; charset="utf-8"



On 2014-12-03 16:24, Juan Pablo Carbajal wrote:
> Hi all,
> 
> I guess is time to release a new sockets package, even if only to 
> remove the deprecation warning.
> 
> Since a while I am trying to get something nice working to connect 
> Octave and Python. I found ?MQ [1] and I thought we should pimp up the 
> socket package to use ?MQ + some package creator (I am looking at JSON 
> and MSGPACK).
> 
> What do you think of this?
> Do you see any problems (like license issues, etc... it shouldn't ?MQ 
> is LGPL) Do you have suggestions?
> 

Hi!
It has been a while since I touched the sockets package. In this case, "no
news is good news".

1)
what do you mean by deprecation warning? it still builds and works fine, as
far as I know? The only open bug I can find is #111 which is related to
mingw. (See point 3 for more on that topic)

2)
?MQ may be a splendid piece of software, but please create a separate
package for it. The sockets package should be used for sockets. Other
packages can depend on it, if they need sockets and can use them from octave
rather than c++.

3)
Carne prepared for a sockets 1.2.0 release almost a year ago. I have
polished a bit on the news, and I think it is fit for release.
Unfortunately I currently do not have easy access to windows. Is it possible
to run the windows release under wine, to be able to test? Or is there some
other octave developer who wants to volunteer trying on windows (especially
mingw)?

With that said, I just pushed 1.2.0 to sourceforge. Please find a tarball
attached to this mail.

Paul


-----

I can give the mingw version a go with octave-3.8.2


-----
On Windows 7, using mxe-octave 3.8.2 (32 bit)
I installed ok from the checked out sources and it compiled ok.
I ran the test_socket script (had to change the #!/ at the top to
/bin/octave for mingw and put a pkg load sockets statement in the script to
ensure it got loaded first.

Results of the run:
bash-3.1$ ./test_socket c
 Columns 1 through 6:

  3.2218e-005  6.7677e-001  7.3719e-001  5.5241e-001  7.9283e-001
8.3625e-001
  6.4849e-001  7.2221e-001  4.6885e-001  4.2583e-001  3.0987e-002
1.4187e-001
  1.2917e-001  9.9200e-001  6.4640e-002  1.7344e-001  2.0264e-001
8.5695e-001
  3.8671e-001  4.0447e-001  5.0458e-001  1.3378e-001  1.6616e-001
6.4120e-001
  7.0409e-001  8.9333e-002  3.3183e-001  6.3939e-002  7.3393e-001
3.4059e-001
  1.2463e-001  9.7025e-001  3.4216e-001  7.9328e-001  9.8767e-001
3.8042e-001
  8.8590e-001  4.5579e-001  3.8386e-001  7.6423e-001  4.3996e-001
6.9208e-001
  9.9179e-001  9.9269e-001  3.2465e-001  5.9755e-001  8.4796e-001
7.4008e-001
  4.0959e-001  7.9372e-001  1.5082e-001  1.3367e-001  9.5680e-001
5.5145e-001
  7.3238e-001  3.1171e-001  6.3433e-001  6.5205e-001  7.1197e-001
9.0706e-001

 Columns 7 through 10:

  9.9136e-001  1.3668e-001  7.5821e-001  1.0705e-001
  9.5474e-001  1.3979e-001  7.6358e-001  9.4191e-001
  8.9543e-001  4.3789e-001  2.7810e-001  5.1517e-001
  2.7501e-001  4.5183e-001  4.7026e-001  6.5646e-001
  4.1868e-001  5.0852e-003  4.6293e-001  1.2624e-001
  4.5408e-002  4.5770e-001  9.0123e-001  2.7931e-001
  6.0573e-001  1.0929e-001  1.5562e-001  6.2640e-001
  9.6715e-001  7.9687e-001  6.4604e-001  8.1296e-001
  4.9404e-002  7.9822e-001  8.1730e-001  9.0250e-001
  7.4347e-001  3.1368e-001  6.7054e-001  1.1226e-001
bash-3.1$