Skip to content

Normalize SocketError enum numeric constants - #239

Open
Burak Soykan (bruak) wants to merge 1 commit into
microsoft:mainfrom
bruak:patch-1
Open

Normalize SocketError enum numeric constants#239
Burak Soykan (bruak) wants to merge 1 commit into
microsoft:mainfrom
bruak:patch-1

Conversation

@bruak

Copy link
Copy Markdown

Replace WSABASEERR offset expressions with their computed Winsock error code values. Expressions such as 10000+4, 10000+13, and 10000+1001 have been replaced with their resolved numeric values such as 10004, 10013, and 11001. This change does not alter the resulting enum values or runtime behavior. It is a readability-only update that makes the SocketError constants easier to compare with documented Winsock error codes.

READ BEFORE FILING

This repository is read-only and doesn't accept community pull requests.

Replace WSABASEERR offset expressions with their computed Winsock error code values. Expressions such as 10000+4, 10000+13, and 10000+1001 have been replaced with their resolved numeric values such as 10004, 10013, and 11001. This change does not alter the resulting enum values or runtime behavior. It is a readability-only update that makes the SocketError constants easier to compare with documented Winsock error codes.
@bruak

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@akoeplinger

Alexander Köplinger (akoeplinger) commented May 12, 2026

Copy link
Copy Markdown
Member

@bruak did you see this:

READ BEFORE FILING
This repository is read-only and doesn't accept community pull requests.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants