From: Petr Sorfa <petrs@caldera.com>
To: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: [RFH] F95 expression parser
Date: Fri, 10 May 2002 11:16:00 -0000 [thread overview]
Message-ID: <3CDC1174.75CC64A1@caldera.com> (raw)
Hi,
Yet another round of questions (and some attempts to answer them on my
part), but this time concerning my F95 expression parser patch.
1) Should I submit it first to FSF for approval? I assume so.
2) Should a separate branch be created for the F95 support? Currently I
don't think this is necessary. The expression parser doesn't really
touch any of the existing files (except for those needed to register a
new language and Makefile stuff.) The patch only introduces the F95
expression parser, not proper F95 support (so eval.c will be minimally
touched.) True support for F95 is coming in separate patches for more
accurate review/approval by relevant owners. Mainly DWARF and eval
stuff.
Petr
next reply other threads:[~2002-05-10 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 11:16 Petr Sorfa [this message]
2002-05-10 11:27 Michael Elizabeth Chastain
2002-05-10 11:33 ` Elena Zannoni
2002-05-10 13:20 ` Jim Blandy
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=3CDC1174.75CC64A1@caldera.com \
--to=petrs@caldera.com \
--cc=gdb-patches@sources.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