usocket-devel March 2007

usocket-devel@common-lisp.net

3 participants
3 discussions

[usocket-devel] :reuseaddress
by Attila Lendvai 29 Mar '07

29 Mar '07

dear list, the :reuseaddress keyword arg does not follow the usual naming convention. what do you think about renaming it to :reuse-address? -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronstället)

1 0

[usocket-devel] allegro.lisp
by Paul O'Rorke 24 Mar '07

24 Mar '07

Hi: I am trying to use usocket to port some projects from CLisp to ACL and possible SBCL and hoping usocket will enable me to have something general. In ACL, there seem to be problems in the get-XXX methods that I think are patched as follows... ; 070315 PaulO: this seems too specific and doesn't match get-local-address ; (defmethod get-peer-address ((usocket stream-server-usocket)) (defmethod get-peer-address ((usocket usocket)) (hbo-to-vector-quad (socket:remote-host (socket usocket)))) (defmethod get-local-port ((usocket usocket)) (socket:local-port (socket usocket))) ; 070315 PaulO: this seems too specific and doesn't match get-local-name ; (defmethod get-peer-port((usocket stream-server-usocket)) (defmethod get-peer-port ((usocket usocket)) (socket:remote-port (socket usocket))) (defmethod get-local-name ((usocket usocket)) (values (get-local-address usocket) (get-local-port usocket))) ; 070315 PaulO: this seems too specific and doesn't match get-local-name ; (defmethod get-peer-name ((usocket stream-server-usocket)) (defmethod get-peer-name ((usocket usocket)) (values (get-peer-address usocket) (get-peer-port usocket)))

2 2

[usocket-devel] SBCL test failures
by Paul O'Rorke 15 Mar '07

15 Mar '07

Hi: I am evaluating usocket as a way to help generalize and port a program that currently uses CLisp and I am using SBCL. I dug up cl-rt and split-sequence in cl-utilities and ran the tests and got the following errors on my Intel MacBook Pro running OS X... Is it just that the tests need to allow SBCL to return timeout error? (I don't see SBCL in the with-caught-conditions.) #<USOCKET:TIMEOUT-ERROR {11862E89}> is a USOCKET:TIMEOUT-ERROR. Its slot values are (:SOCKET #<USOCKET:STREAM-USOCKET {11862A31}>). Test USOCKET-TEST::SOCKET-FAILURE.1 failed Form: (USOCKET-TEST::WITH-CAUGHT-CONDITIONS ('USOCKET:NETWORK-UNREACHABLE-ERROR NIL) (USOCKET:SOCKET-CONNECT 2130706432 USOCKET-TEST::+UNUSED-LOCAL-PORT+) :UNREACH) Expected value: NIL Actual value: #<USOCKET:TIMEOUT-ERROR {11862E89}>. #<USOCKET:TIMEOUT-ERROR {1195CCB1}> is a USOCKET:TIMEOUT-ERROR. Its slot values are (:SOCKET #<USOCKET:STREAM-USOCKET {1195C761}>). Test USOCKET-TEST::SOCKET-FAILURE.2 failed Form: (USOCKET-TEST::WITH-CAUGHT-CONDITIONS ('USOCKET:HOST-UNREACHABLE-ERROR NIL) (USOCKET:SOCKET-CONNECT USOCKET-TEST::+NON-EXISTING-HOST+ 80) :UNREACH) Expected value: NIL Actual value: #<USOCKET:TIMEOUT-ERROR {1195CCB1}>. The only other test that failed was: (deftest socket-name.4 (with-caught-conditions (nil nil) (let ((sock (usocket:socket-connect +common-lisp-net+ 80))) (unwind-protect (usocket::get-local-address sock) (usocket:socket-close sock)))) #(192 168 1 65)) Should I have replaced the 192 168 1 65 with my machine's local IP? ---Paul O

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

usocket-devel March 2007