From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 3/4] Update comments to TERNOP_SLICE
Date: Wed, 16 Jul 2014 05:19:00 -0000 [thread overview]
Message-ID: <1405487742-32613-4-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <1405487742-32613-1-git-send-email-yao@codesourcery.com>
TERNOP_SLICE was added for language Chill, but it is used for Ada and D later.
Since language Chill was removed from GDB, TERNOP_SLICE is only used for
Ada and D. This patch is to update its comments.
gdb:
2014-07-15 Yao Qi <yao@codesourcery.com>
* std-operator.def: Update comments to TERNOP_SLICE.
---
gdb/std-operator.def | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/std-operator.def b/gdb/std-operator.def
index c33a287..24c3a2b 100644
--- a/gdb/std-operator.def
+++ b/gdb/std-operator.def
@@ -93,8 +93,8 @@ OP (BINOP_END)
/* Operates on three values computed by following subexpressions. */
OP (TERNOP_COND) /* ?: */
-/* A sub-string/sub-array. (the deleted) Chill syntax:
- OP1(OP2:OP3). Return elements OP2 through OP3 of OP1. */
+/* A sub-string/sub-array. Ada syntax: OP1(OP2..OP3). Return
+ elements OP2 through OP3 of OP1. */
OP (TERNOP_SLICE)
/* Multidimensional subscript operator, such as Modula-2 x[a,b,...].
--
1.9.0
next prev parent reply other threads:[~2014-07-16 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 5:19 [PATCH 0/4] Remove operators for language chill Yao Qi
2014-07-16 5:19 ` [PATCH 2/4] Remove operator BINOP_RANGE Yao Qi
2014-07-16 5:19 ` Yao Qi [this message]
2014-07-16 5:19 ` [PATCH 1/4] Remove operator BINOP_IN Yao Qi
2014-07-16 8:53 ` [PATCH 4/4] Remove Chill from comments Yao Qi
2014-07-19 9:17 ` [PATCH 0/4] Remove operators for language chill Tom Tromey
2014-07-20 23:47 ` Yao Qi
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=1405487742-32613-4-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@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: 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