From: Richard Henderson <rth@redhat.com>
To: gdb-patches@gcc.gnu.org
Subject: Re: [RFA] print function arguments for g95
Date: Tue, 14 Oct 2003 06:53:00 -0000 [thread overview]
Message-ID: <20031014065331.GA27340@redhat.com> (raw)
In-Reply-To: <20031013160601.GA21537@nevyn.them.org>
On Mon, Oct 13, 2003 at 12:06:01PM -0400, Daniel Jacobowitz wrote:
> Does f_type_print_base take care of printing a closing paren or do you
> need one here?
f_type_print_varspec_suffix does it. And there was already an
entry for TYPE_CODE_REF there.
r~
prev parent reply other threads:[~2003-10-14 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 8:55 Richard Henderson
2003-10-13 16:06 ` Daniel Jacobowitz
2003-10-14 6:53 ` Richard Henderson [this message]
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=20031014065331.GA27340@redhat.com \
--to=rth@redhat.com \
--cc=gdb-patches@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: 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