Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Petr Sorfa <petrs@caldera.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [RFC] FORTRAN95 Expression parser
Date: Tue, 30 Apr 2002 06:40:00 -0000	[thread overview]
Message-ID: <3CCEA15F.A299E742@caldera.com> (raw)
In-Reply-To: <3CCDF533.4D5C2851@redhat.com>

Hi Michael,

> > I've created a FORTRAN95 expression parser for GDB. It is based off the
> > current FORTRAN expression parser, but has changed significantly in
> > source and functionality. I've developed it as a new separate parser
> > with the file prefix of f95-x as opposed to the existing f-x files.
> >
> > The question is whether I should submit the patch as the f95-x files
> > (which will leave the current FORTRAN parser untouched) or replace the
> > existing FORTRAN parser?
> >
> > Note that the F95 parser fully supports F77/F90/F95, but differs a bit
> > from the existing fortran gdb parser (which relies a bit heavily on C
> > notation.)
> 
> How much does it differ?  Functionally?  In user-visible ways?
> How about test suites?
It differs considerably - it supports FORTRAN expressions, not C
expressions that handle FORTRAN stuff. It supports FORTRAN intrinsics
(KIND, SIZE, LEN, ALLOCATED, ASSOCIATED, etc..). Proper FORTRAN array
subscripts (including stride). Proper print out of FORTRAN types and
variables. Supports column major notation. Supports MODULES, CONTAINS,
TYPE records, and so on.

User visible ways are considerably different, like I said, it treats
expressions like FORTRAN would.

I've added around 500 new test cases.

Petr


  reply	other threads:[~2002-04-30 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29 11:57 Petr Sorfa
2002-04-29 18:49 ` Michael Snyder
2002-04-30  6:40   ` Petr Sorfa [this message]
2002-04-30 10:50     ` Michael Snyder
2002-04-30 11:02     ` Stan Shebs
2002-04-30 11:11 Michael Elizabeth Chastain
2002-04-30 12:01 ` Petr Sorfa
2002-04-30 12:13   ` Michael Snyder

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=3CCEA15F.A299E742@caldera.com \
    --to=petrs@caldera.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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