From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 8/8] Rename OP_F90_RANGE to OP_RANGE.
Date: Wed, 27 Apr 2016 21:26:00 -0000 [thread overview]
Message-ID: <399e9af8-122d-56c7-2610-fdd0ab08b404@redhat.com> (raw)
In-Reply-To: <1461789279-15996-9-git-send-email-tom@tromey.com>
On 04/27/2016 09:34 PM, Tom Tromey wrote:
> This renames OP_F90_RANGE to OP_RANGE, and similarly renames the
> f90_range_type enum.
>
> 2016-04-27 Tom Tromey <tom@tromey.com>
>
> * std-operator.def (OP_RANGE): Rename from OP_F90_RANGE.
> * rust-lang.c: Don't include f-lang.h.
> (rust_range, rust_compute_range, rust_subscript)
> (rust_evaluate_subexp): Update.
> * rust-exp.y: Don't include f-lang.h.
> (ast_range, convert_ast_to_expression): Update.
> * parse.c (operator_length_standard): Update.
> * f-lang.h (enum f90_range_type): Move to expression.h.
> * f-exp.y: Use OP_RANGE.
> * expression.h (enum range_type): New enum; renamed from
> f90_range_type.
> * expprint.c: Don't include f-lang.h.
> (print_subexp_standard, dump_subexp_body_standard): Use OP_RANGE.
> * eval.c (value_f90_subarray, evaluate_subexp_standard): Update.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-04-27 21:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 20:35 [PATCH v2 0/8] Add Rust language support Tom Tromey
2016-04-27 20:35 ` [PATCH v2 6/8] Update gdb test suite for Rust Tom Tromey
2016-04-27 20:35 ` [PATCH v2 1/8] Fix latent yacc-related bug in gdb/Makefile.in init.c rule Tom Tromey
2016-04-27 20:35 ` [PATCH v2 3/8] Add self-test framework to gdb Tom Tromey
2016-04-28 5:00 ` Eli Zaretskii
2016-04-28 10:28 ` Yao Qi
2016-04-29 15:13 ` Tom Tromey
2016-04-29 15:29 ` Yao Qi
2016-04-29 17:29 ` Doug Evans
2016-04-29 20:40 ` Tom Tromey
2016-04-29 20:54 ` Simon Marchi
2016-04-29 21:09 ` Tom Tromey
2016-05-03 15:58 ` Yao Qi
2016-04-27 20:35 ` [PATCH v2 7/8] Add Rust documentation Tom Tromey
2016-04-28 4:59 ` Eli Zaretskii
2016-04-27 20:35 ` [PATCH v2 2/8] Make gdb expression debugging handle OP_F90_RANGE Tom Tromey
2016-04-27 20:35 ` [PATCH v2 8/8] Rename OP_F90_RANGE to OP_RANGE Tom Tromey
2016-04-27 21:26 ` Pedro Alves [this message]
2016-04-27 20:35 ` [PATCH v2 4/8] Add array start and end strings to generic_val_print_decorations Tom Tromey
2016-04-27 20:36 ` [PATCH v2 5/8] Add support for the Rust language Tom Tromey
2016-04-27 21:27 ` [PATCH v2 0/8] Add Rust language support Pedro Alves
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=399e9af8-122d-56c7-2610-fdd0ab08b404@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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