public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49213] [OOP][F2008] gfortran rejects structure constructor expression
Date: Thu, 16 Jun 2011 19:44:00 -0000	[thread overview]
Message-ID: <bug-49213-4-dOWdyKNGEF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49213-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49213

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011.06.16 19:43:45
            Summary|[OOP] gfortran rejects      |[OOP][F2008] gfortran
                   |structure constructor       |rejects structure
                   |expression                  |constructor expression
     Ever Confirmed|0                           |1

--- Comment #1 from janus at gcc dot gnu.org 2011-06-16 19:43:45 UTC ---
Note: Intrinsic assignments to polymorphic variables are forbidden in the
Fortran 2003 standard, and currently not supported by gfortran, cf. PR 43366.

F03:7.4.1.2:
"In an intrinsic assignment statement, variable shall not be polymorphic, and
..."


  reply	other threads:[~2011-06-16 19:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28 18:15 [Bug fortran/49213] New: [OOP] " neil.n.carlson at gmail dot com
2011-06-16 19:44 ` janus at gcc dot gnu.org [this message]
2011-06-16 19:50 ` [Bug fortran/49213] " janus at gcc dot gnu.org
2011-06-16 20:36 ` neil.n.carlson at gmail dot com
2011-06-16 20:50 ` neil.n.carlson at gmail dot com
2011-06-16 21:29 ` janus at gcc dot gnu.org
2011-06-16 22:14 ` neil.n.carlson at gmail dot com
2011-06-16 22:18 ` neil.n.carlson at gmail dot com
2013-01-10 15:46 ` janus at gcc dot gnu.org
2013-01-10 16:07 ` janus at gcc dot gnu.org
2013-01-10 20:40 ` janus at gcc dot gnu.org
2013-01-11 12:04 ` janus at gcc dot gnu.org
2013-08-05  9:08 ` janus at gcc dot gnu.org
2013-08-05  9:22 ` janus at gcc dot gnu.org
2013-08-05 11:14 ` janus at gcc dot gnu.org
2013-08-06  8:42 ` janus at gcc dot gnu.org
2013-08-06  9:13 ` janus at gcc dot gnu.org
2013-08-06 10:50 ` janus at gcc dot gnu.org
2013-08-08 16:54 ` dominiq at lps dot ens.fr
2013-08-11 17:03 ` dominiq at lps dot ens.fr
2015-01-24 11:52 ` dominiq at lps dot ens.fr
2015-01-24 16:32 ` dominiq at lps dot ens.fr
2015-01-24 19:05 ` janus at gcc dot gnu.org
2015-02-05  8:09 ` pault at gcc dot gnu.org
2020-03-12 11:58 ` jakub at gcc dot gnu.org
2021-04-16 20:03 ` vladimir.fuka at gmail dot com
2021-06-01  8:05 ` rguenth at gcc dot gnu.org
2022-05-27  9:12 ` rguenth at gcc dot gnu.org
2023-06-22 16:45 ` pault at gcc dot gnu.org
2023-06-28 11:39 ` cvs-commit at gcc dot gnu.org
2023-10-31  8:23 ` pault at gcc dot gnu.org
2023-10-31  8:24 ` pault at gcc dot gnu.org
2023-10-31  8:29 ` pault 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-49213-4-dOWdyKNGEF@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: link
Be 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).