public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39490] Invalid character constructor rejected at -std=gnu since 4.4 Date: Sat, 28 Mar 2009 08:28:00 -0000 [thread overview] Message-ID: <20090328082806.11604.qmail@sourceware.org> (raw) In-Reply-To: <bug-39490-17466@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from fxcoudert at gcc dot gnu dot org 2009-03-28 08:28 ------- This is work that Daniel Kraft and I did (well, I think he did the hard work and I gave some loose sort of guidance). I seem to remember it was intentional (it may have been discussed on the list around summer of 2008, but I can't find it). Regarding whether it's desirable or not, I think it is right to issue an error: this is rather recent Fortran code, so people have virtually no reason for not writing the proper constructor. (Accepting invalid code as a GNU extension should be done sparsely.) I'm thus closing as WONTFIX. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu dot | |org Status|UNCONFIRMED |RESOLVED GCC build triplet|Linux, x86_64 and i486 | GCC host triplet|Linux, x86_64 and i486 | GCC target triplet|Linux, x86_64 and i486 | Resolution| |WONTFIX Summary|Non-standard assignment of |Invalid character |arrays of character objects |constructor rejected at - | |std=gnu since 4.4 Version|4.3.2 |4.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39490
prev parent reply other threads:[~2009-03-28 8:28 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-18 9:53 [Bug fortran/39490] New: Non-standard assignment of arrays of character objects n dot pinhao at netvisao dot pt 2009-03-18 11:17 ` [Bug fortran/39490] " dominiq at lps dot ens dot fr 2009-03-18 19:13 ` burnus at gcc dot gnu dot org 2009-03-28 8:28 ` fxcoudert at gcc dot gnu dot 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=20090328082806.11604.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).