public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104709] A translated error message will include untanslated parts Date: Fri, 04 Mar 2022 10:37:52 +0000 [thread overview] Message-ID: <bug-104709-4-bGYDsy3CFO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104709-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104709 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- A better way would be not to pass around errmsg but instead an enum what exact error it is and then just handle all of those in a switch. Like e.g. required_token in cp/parser.cc (cp_parser_required_error) etc.
next prev parent reply other threads:[~2022-03-04 10:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-27 10:51 [Bug c++/104709] New: " goeran at uddeborg dot se 2022-02-28 9:21 ` [Bug c++/104709] " redi at gcc dot gnu.org 2022-03-04 10:10 ` redi at gcc dot gnu.org 2022-03-04 10:37 ` jakub at gcc dot gnu.org [this message] 2022-03-11 10:47 ` 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-104709-4-bGYDsy3CFO@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).