New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opening a tcp connection to a down host results in NIL on LW 6 #37

Closed
quicklisp opened this Issue May 23, 2011 · 1 comment

Comments

Projects
None yet
1 participant
@quicklisp
Owner

quicklisp commented May 23, 2011

Per Ala'a Mohammad Alawi:

Hi Zach

quicklisp implementation of open-connection for LispWorks uses
open-tcp-stream. which will fail silently (returning nil) in case of
unkwon-host (a site was down). adding :errorp to the call will help
the user by show a readable error message. I've tried sbcl and ccl
where both the error was more indicative than complaining about a
stream being a 'nil' (as was the case with Lispworks)

Verify that the :errorp option works on each version of LispWorks and update the code to use it.

@quicklisp

This comment has been minimized.

Show comment
Hide comment
@quicklisp

quicklisp Dec 2, 2013

Owner

This is an easy fix with :errorp, just do it!

Owner

quicklisp commented Dec 2, 2013

This is an easy fix with :errorp, just do it!

quicklisp pushed a commit that referenced this issue Dec 13, 2013

@quicklisp quicklisp closed this Dec 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment