Skip to content

Releases: NotMePipe/cross-socket

CrossSocket v1.2

28 Jul 16:02
776684a

Choose a tag to compare

Version 1.2

  • #include improvements
  • Bug fixes
  • Error messages return error numbers every time
  • (1.0W2) has been resolved.
  • (1.0W4) has been resolved.
  • (1.0W7) has been resolved.

CrossSocketUtils.h

  • Terrible macro redefinitions have been removed
  • Wrappers for ntohl() and htonl() have been added
  • All error codes now have the CSE prefix

Socket.h

  • Error() now requires an error code to be passed

Warnings

  • (1.1W1) Extended: CSECONNREFUSED has been determined to be safe, but it is still used in an inconvenient way in Socket::ConnectTo(). This is intended to be removed in the next version (1.2W1)
  • Socket::Error() shuts down CrossSocket whenever it is called. While this isn't a bug, it is not an intended behavior and will be removed in the next version (1.2W2)
  • CrossSocket will be converting to implement RAII very soon. Functions which do not match that implementation may be removed without notice (1.2W3)

What's Changed

Full Changelog: v1.1...v1.2
https://github.com/NotMePipe/cross-socket/blob/main/Changelog.md

CrossSocket v1.1

09 Jul 12:43
225339e

Choose a tag to compare

Version 1.1

  • Renamed CrossSocket.h to Socket.h
  • Sockets are now shut down before they are closed
  • Added Doxygen comments
  • (1.0W8) has been resolved.

CrossSocketUtils.h

  • Added ECONNREFUSED macro
  • close_socket() has been moved into the CS_Utils class for call safety
  • All CS_Utils contents have been made private for call safety
    • CrossSocket files have been marked as friends to this class

Socket.h

  • Renamed CloseSocket() to Close()
  • Added Shutdown() for manual shutdown calls
  • Close() now checks if the socket_t is valid before trying to close it

SocketManager.h

  • Improved memory practices
  • Added CloseSockets() to close all Sockets handle by the SocketManager
  • Users should no longer close Sockets twice when using the SocketManager
    • CrossSocket now intelligently handles this. Closing a Socket twice will not cause any errors, but it is unnecessary and a bad practice

What's Changed

Full Changelog: