Skip to content
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.

Sign up for GitHub

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

Jump to bottom

wrong return value sf::SocketTCP::Connect on linux (ubuntu) #26

Closed
coyotte508 opened this issue Apr 10, 2011 · 1 comment
Closed

wrong return value sf::SocketTCP::Connect on linux (ubuntu) #26

coyotte508 opened this issue Apr 10, 2011 · 1 comment
Labels
s:rejected

Comments

@coyotte508
Copy link

On linux, sf::SocketTCP::Connect() returns false when successful, and true when unsuccessful. (The doc says it should be true on success and false on failure)

SFML Version 1.6, Linux (ubuntu).
@LaurentGomila
Copy link
Member

sf::SocketTCP returns a sf::Socket::Status, not a boolean.

The doc will be fixed accordingly.

lioncash added a commit to lioncash/dolphin that referenced this issue Feb 10, 2014
@lioncash
Clarify an if statement in NetPlayClient.cpp. See: SFML/SFML#26.
8159fe8 
This was simply an error in documentation. It actually returns an sf::Socket::Status enum value as a result.
lioncash added a commit to lioncash/dolphin that referenced this issue Feb 10, 2014
@lioncash
Clarify an if statement in NetPlayClient.cpp. See: SFML/SFML#26.
82f5630 
This was simply an error in documentation. It actually returns an sf::Socket::Status enum value as a result.
lioncash added a commit to lioncash/dolphin that referenced this issue Feb 10, 2014
@lioncash
Clarify an if statement in NetPlayClient.cpp. See: SFML/SFML#26.
f5408c3 
This was simply an error in documentation. It actually returns an sf::Socket::Status enum value as a result.
@lioncash lioncash mentioned this issue Feb 10, 2014
Merged
@miki151 miki151 mentioned this issue Jan 11, 2015
Closed
@fallahn fallahn mentioned this issue Dec 8, 2015
Closed
@vittorioromeo vittorioromeo mentioned this issue Jun 8, 2024
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
s:rejected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LaurentGomila @coyotte508