public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jscott at posteo dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/30247] New: all socket options should be available with _XOPEN_SOURCE. not merely _GNU_SOURCE Date: Mon, 20 Mar 2023 00:24:41 +0000 [thread overview] Message-ID: <bug-30247-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30247 Bug ID: 30247 Summary: all socket options should be available with _XOPEN_SOURCE. not merely _GNU_SOURCE Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: network Assignee: unassigned at sourceware dot org Reporter: jscott at posteo dot net Target Milestone: --- Hi, POSIX Issue 7 says that identifiers starting with 'SO' (no underscore required) are reserved to the implementation (only if XSI conformance is requested; _POSIX_C_SOURCE isn't good enough). Thus, that means it is safe to expose socket options like SO_PROTOCOL, and in fact it would be helpful for application maintainers who want to use this enhanced functionality (like me!) Note that SO_PROTOCOL in particular is planned for POSIX Issue 8, but this bug is about unleashing all socket options to XSI applications. Thanks -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-03-20 0:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-20 0:24 jscott at posteo dot net [this message] 2023-03-21 4:18 ` [Bug network/30247] " sam at gentoo dot org 2023-04-04 9:58 ` schwab@linux-m68k.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30247-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).