public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/107008] Combine config/os/*/error_constants.h into one file Date: Thu, 22 Sep 2022 10:44:12 +0000 [thread overview] Message-ID: <bug-107008-4-b5yOU9vbvn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107008-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107008 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- A related topic is that we simply don't define the errc enumerators that don't have a corresponding EXXXX macro, which is non-conforming. The C++ standard says the enumerators should all be there. We could do something like this for each enumerator: #ifdef EFOO foo = EFOO, #else foo = _GLIBCXX_ERRC_ORIGIN + __LINE__, #endif Where _GLIBCXX_ERRC_ORIGIN is some value intended to be higher than the highest errno value on the OS. We only need fewer than 100 errc enumerators so INT_MAX/2 might be OK. We can use #line to set the __LINE__ to a fixed value in the file, so that the constants don't change if we add/remove lines before the errc definition.
next prev parent reply other threads:[~2022-09-22 10:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-22 10:33 [Bug libstdc++/107008] New: " redi at gcc dot gnu.org 2022-09-22 10:38 ` [Bug libstdc++/107008] " redi at gcc dot gnu.org 2022-09-22 10:44 ` redi at gcc dot gnu.org [this message] 2022-09-22 10:45 ` redi at gcc dot gnu.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-107008-4-b5yOU9vbvn@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).