Hello,
any idea why sb-bsd-socket:protocol-unknown was added to +sbcl-condition-map+ in r302? It breaks usocket compilation on SBCL 1.0.14.26 on my system, and sbcl/contrib/sb-bsd-sockets/sockets.lisp does not define such socket condition.
Regards, Victor.
On Wed, Feb 13, 2008 at 5:30 AM, Victor Kryukov victor.kryukov@gmail.com wrote:
Hello,
any idea why sb-bsd-socket:protocol-unknown was added to +sbcl-condition-map+ in r302?
Because I'm an idiot! Or at least, I reversed the order of the words. It should have been 'unknown-protocol'...
It breaks usocket compilation on SBCL 1.0.14.26 on my system, and sbcl/contrib/sb-bsd-sockets/sockets.lisp does not define such socket condition.
Yep. I'll change the wording from one to the other.
Thanks for your report!
bye,
Erik.
On Fri, Feb 15, 2008 at 11:17 AM, Erik Huelsmann ehuels@gmail.com wrote:
On Wed, Feb 13, 2008 at 5:30 AM, Victor Kryukov victor.kryukov@gmail.com wrote:
Hello,
any idea why sb-bsd-socket:protocol-unknown was added to +sbcl-condition-map+ in r302?
Because I'm an idiot! Or at least, I reversed the order of the words. It should have been 'unknown-protocol'...
It breaks usocket compilation on SBCL 1.0.14.26 on my system, and sbcl/contrib/sb-bsd-sockets/sockets.lisp does not define such socket condition.
Yep. I'll change the wording from one to the other.
r306 should fix the SBCL build again.
bye,
Erik.
-
Erik Huelsmann -
Victor Kryukov