public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39490] Non-standard assignment of arrays of character objects Date: Wed, 18 Mar 2009 11:17:00 -0000 [thread overview] Message-ID: <20090318111707.22431.qmail@sourceware.org> (raw) In-Reply-To: <bug-39490-17466@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from dominiq at lps dot ens dot fr 2009-03-18 11:17 ------- Confirmed on 4.3.3, trunk gives: pr39490.f90:1.36: CHARACTER(14) :: prop(4) = (/'name', 'data_file_name', 'Ho_units', 'mpolar_unit 1 Error: Different CHARACTER lengths (4/14) in array constructor at (1) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39490
next prev parent reply other threads:[~2009-03-18 11:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-18 9:53 [Bug fortran/39490] New: " n dot pinhao at netvisao dot pt 2009-03-18 11:17 ` dominiq at lps dot ens dot fr [this message] 2009-03-18 19:13 ` [Bug fortran/39490] " burnus at gcc dot gnu dot org 2009-03-28 8:28 ` [Bug fortran/39490] Invalid character constructor rejected at -std=gnu since 4.4 fxcoudert at gcc dot gnu dot 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=20090318111707.22431.qmail@sourceware.org \ --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).