From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>,
Arnaud Charlet <charlet@adacore.com>
Subject: Re: make conflicting help text an error
Date: Sun, 13 May 2012 11:03:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1205131102510.23868@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAESRpQAS8m0Gyy3LLZkiVjwoOs4OUYTzZAd3aHTdAwm-JH0F2Q@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 943 bytes --]
On Sun, 13 May 2012, Manuel López-Ibáñez wrote:
> Hi,
>
> These warnings are invisible when building but they may help to detect
> if an option is duplicated somewhere else with different purpose , so
> it would be better to make this an error,
>
> Only 2 options in Ada trigger this warning, and their help text has no
> effect, since it gest overridden by the ones in c.opt. Fixing this
> properly would require language-specific namespace, so two options
> with the same name in different languages can have completely
> different help text (and Init() and other flags). Not something I am
> planning to work on in the future.
>
> OK?
This is OK. I don't think we want to support different help strings for
different languages; if an option is supported for multiple languages, we
should have a generic description of that option that is correct for all
of them.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-05-13 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 9:05 Manuel López-Ibáñez
2012-05-13 11:03 ` Joseph S. Myers [this message]
2022-03-30 21:09 ` options: Clarifications around option definition records' help texts (was: make conflicting help text an error) Thomas Schwinge
2022-03-31 17:18 ` Joseph Myers
2022-03-30 20:42 ` options: Fix "Multiple different help strings" error diagnostic " Thomas Schwinge
2022-03-31 17:17 ` Joseph Myers
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=Pine.LNX.4.64.1205131102510.23868@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=charlet@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=lopezibanez@gmail.com \
/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: link
Be 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).