public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/101735] New: Type parameter inquiries for substrings are rejected Date: Mon, 02 Aug 2021 21:08:34 +0000 [thread overview] Message-ID: <bug-101735-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735 Bug ID: 101735 Summary: Type parameter inquiries for substrings are rejected Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: anlauf at gcc dot gnu.org Target Milestone: --- As noted by Tobias Burnus in pr100950, type parameter inquiries (see e.g. F2018:9.4.5) are not recognized for substrings. character(len=5) :: str integer, parameter :: j = str% kind ! accepted (ok) integer, parameter :: k = str% len ! accepted (ok) integer, parameter :: l = str(1:3)% len ! not accepted integer, parameter :: m = str(1:3)% kind ! not accepted end gives: pr100950-inq.f90:4:25: 4 | integer, parameter :: l = str(1:3)% len ! not accepted | 1 Error: Parameter 'str' at (1) has not been declared or is a variable, which does not reduce to a constant expression pr100950-inq.f90:5:25: 5 | integer, parameter :: m = str(1:3)% kind ! not accepted | 1 Error: Parameter 'str' at (1) has not been declared or is a variable, which does not reduce to a constant expression
next reply other threads:[~2021-08-02 21:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 21:08 anlauf at gcc dot gnu.org [this message] 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 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@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: linkBe 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).