This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Parsing Fortran

From: Richard E Maine <Richard dot Maine at nasa dot gov>
To: Joe Krahn <krahn at niehs dot nih dot gov>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, fortran at gcc dot gnu dot org
Date: Mon, 17 Jul 2006 12:53:52 -0700
Subject: Re: Parsing Fortran
References: <44B80421.8090404@niehs.nih.gov> <276C4272-B70A-4540-91A3-CE889AF0672A@physics.uc.edu> <44BBDACE.2010000@niehs.nih.gov>

On Jul 17, 2006, at 11:45 AM, Joe Krahn wrote:

In general, my plan is to use YACC for lexing characters into context-independent generic expressions... Using YACC this way, errors only occur when there really is uninterpretable gibberish. For example, if a triplet-spec is seen where it is invalid, it still be recognized as a triplet-spec, instead of just seeing ':' as an unexpected character.

But triplet-spec is not context independent, so I don't see how this is going to work. There are things that can look just like a triplet- spec and are distinguished only by context.

For example, a substring-spec (or whatever they are called - not worth looking up) looks like a special case of a triplet-spec. So can some cases of a dimension.

--
Richard Maine                |  Good judgment comes from experience;
Richard.Maine@nasa.gov       |  experience comes from bad judgment.
                            |        -- Mark Twain

References:
- Parsing Fortran
  - From: Joe Krahn
- Re: Parsing Fortran
  - From: Andrew Pinski
- Re: Parsing Fortran
  - From: Joe Krahn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]