public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99765] Explicit dimension size declaration of pointer array allowed Date: Fri, 26 Mar 2021 07:36:05 +0000 [thread overview] Message-ID: <bug-99765-4-vkf1IwrULK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99765-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99765 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Nick from comment #4) > I see. I can't seem to find the mentioned line in f2003. Should be there as well. In Fortran 2008, it is in "5.2 Type declaration statements", p.88, lines 1-4 (same/similar to F2018). In Fortran 2003, it is in "5.1.2.5 DIMENSION attribute", p. 78, ll. 3-5: "The DIMENSION attribute specifies that an entity is an array. The rank or rank and shape is specified by the array-spec, if there is one, in the entity-decl, or by the array-spec in the DIMENSION attr-spec otherwise." That choice makese sense, e.g. for: complex(kind=my_cmplx_kind), intent(in), asynchronous, dimension(n,n) :: A, B, C, D, v(n) such that one does not need to repeat all the lengthy stuff just to denote the different array spec for 'v'. (On the other hand, whether there is a need to specify everything in several different ways and permit overriding in addition is another question.) Thus, the standard made a sensible choice – and the standard is the standard :-) > In any case, I would be fine if this is marked as invalid Done so: CLOSE as INVALID. > Sorry for the blurp. Better some noise than missing some real bugs or useful improvements. Hence: Thanks!
prev parent reply other threads:[~2021-03-26 7:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-25 9:22 [Bug fortran/99765] New: " nickpapior at gmail dot com 2021-03-25 11:43 ` [Bug fortran/99765] " dominiq at lps dot ens.fr 2021-03-25 11:47 ` nickpapior at gmail dot com 2021-03-25 15:48 ` burnus at gcc dot gnu.org 2021-03-26 6:41 ` nickpapior at gmail dot com 2021-03-26 7:36 ` burnus at gcc dot gnu.org [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=bug-99765-4-vkf1IwrULK@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).