public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/101735] Type parameter inquiries for substrings are rejected
Date: Mon, 02 Aug 2021 21:35:36 +0000	[thread overview]
Message-ID: <bug-101735-4-ygKbJFbOKb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101735-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #1)
> Furthermore:
> 
> character(len=5) :: str
> print *, str% len      ! accepted (ok)
> print *, str(1:3)% len ! syntax error!?
> end
> 
> produces:
> 
> pr101735-tb.f90:3:18:
> 
>     3 | print *, str(1:3)% len ! syntax error!?
>       |                  1
> Error: Syntax error in PRINT statement at (1)

I think it is a bug in gfortran.  F2018 shows designator % type-param-name
with blanks around %.  For fixed-form source code, blanks are irrelevant.
For free-form source code, 6.3.2.2 has "Blanks may be inserted freely between
tokens to improve readability; for example, blanks may occur between the
tokens that form a complex literal constant."

So, I would think we treat % as a token.

  parent reply	other threads:[~2021-08-02 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 21:08 [Bug fortran/101735] New: " anlauf at gcc dot gnu.org
2021-08-02 21:13 ` [Bug fortran/101735] " anlauf at gcc dot gnu.org
2021-08-02 21:35 ` kargl at gcc dot gnu.org [this message]
2021-08-19  6:43 ` burnus at gcc dot gnu.org

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=bug-101735-4-ygKbJFbOKb@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).