public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Harald Anlauf via Fortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: improve checking of assumed size array spec [PR102180]
Date: Mon, 12 Dec 2022 12:07:06 -0800	[thread overview]
Message-ID: <Y5eJ6lo4jvXwX3ly@troutmask.apl.washington.edu> (raw)
In-Reply-To: <16de1714-fb7d-de19-d8ab-0034bf082fd2@gmx.de>

On Mon, Dec 12, 2022 at 08:49:50PM +0100, Harald Anlauf via Fortran wrote:
> 
> Committed as r13-4623-gcf5327b89ab610.
> 

To be clear, I have no problems with this commit.

But, just a FYI, there is gfc_peek_ascii_char(),
which allows you to look at the next character
without having to keep track of the locus.

> +    {
> +      locus old_loc = gfc_current_locus;
> +      if (gfc_match_char ('*') == MATCH_YES)

         gfc_gobble_whitespace (); /* Can't remember if matching up to this
                                      eats whitespace.  */ 
         if (gfc_peek_ascii_char () == '*')

> +	{
> +	  /* F2018:R821: "assumed-implied-spec  is  [ lower-bound : ] *".  */
> +	  gfc_error ("A lower bound must precede colon in "
> +		     "assumed-size array specification at %L", &old_loc);
> +	  return AS_UNKNOWN;
> +	}
> +      else
> +	{
          gfc_current_locus = old_loc; /* Is this needed? */
> +	  return AS_DEFERRED;
> +	}
> +    }


-- 
Steve

      reply	other threads:[~2022-12-12 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 22:33 Harald Anlauf
2022-12-11 23:52 ` Steve Kargl
2022-12-12 19:49   ` Harald Anlauf
2022-12-12 20:07     ` Steve Kargl [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=Y5eJ6lo4jvXwX3ly@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).