From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: merge std-operator.def and ada-operator.def?
Date: Mon, 19 Mar 2012 15:34:00 -0000 [thread overview]
Message-ID: <20120319153347.GW2853@adacore.com> (raw)
In-Reply-To: <20120319084514.GA29240@host2.jankratochvil.net>
> (a) It would make some sense with GDB plugins but that plan was IIRC abandoned
> in the favor of Python scripting.
>
> (b) The Ada operators should be at least very each marked as Ada specific in
> its definition comment. Moreover I believe it would be worth really
> renaming them all to OP_ADA_* instead.
I am OK with renaming them using OP_ADA_ as a prefix, but I would
go the other way. Instead of having language-specific operators,
make them available to everyone with standard, well documented,
semantics. Many of them might be only used in Ada at the moment,
but I think that's OK and there is no reason that some operators
such as "UNOP_IN_RANGE" for instance might not be used by other
languages.
--
Joel
next prev parent reply other threads:[~2012-03-19 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 23:21 Joel Brobecker
2012-03-16 23:21 ` [RFC 2/2] Remove op_name callback in struct exp_descriptor Joel Brobecker
2012-03-16 23:21 ` [RFC 1/2] merge std-operator.def & ada-operator.def into one file Joel Brobecker
2012-03-16 23:29 ` RFC: merge std-operator.def and ada-operator.def? Joel Brobecker
2012-03-19 8:46 ` Jan Kratochvil
2012-03-19 15:34 ` Joel Brobecker [this message]
2012-03-19 15:40 ` Jan Kratochvil
2012-03-19 15:50 ` Joel Brobecker
2012-03-19 15:58 ` Jan Kratochvil
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=20120319153347.GW2853@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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