public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60238] Allow colon-separated triplet in array initialization Date: Mon, 17 Feb 2014 11:25:00 -0000 [thread overview] Message-ID: <bug-60238-4-QBxMWEg93D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60238-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60238 --- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > as an alternative to the ugly > > indices = (/ (I, I=3, 5) /) You can use indices=[(I, I=3, 5)] if your coding style accepts f2003 syntax. > Supporting it would allow easier compiler interoperability. The only way to achieve that is to stick to the Fortran standard, i.e, never use extensions of any kind.
next prev parent reply other threads:[~2014-02-17 11:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-17 11:10 [Bug fortran/60238] New: " antony at cosmologist dot info 2014-02-17 11:25 ` dominiq at lps dot ens.fr [this message] 2014-02-19 10:07 ` [Bug fortran/60238] " dominiq at lps dot ens.fr 2014-12-06 14:40 ` dominiq at lps dot ens.fr
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-60238-4-QBxMWEg93D@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).