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/58557] [OOP] Issues with CLASS/TYPE functions in array constructors: reject valid, memory leaks, invalid free Date: Sun, 05 Jan 2014 13:07:00 -0000 [thread overview] Message-ID: <bug-58557-4-7UlZfWlyaN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58557-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58557 --- Comment #2 from janus at gcc dot gnu.org --- I think the conversion errors are simply due to declaration issues in the test case, e.g.: program main implicit none type t end type t interface function f_type_na() import :: t type(t) :: f_type end function end interface type(t) :: b b = f_type_na() end program b = f_type_na() 1 Error: Can't convert REAL(4) to TYPE(t) at (1) But the following variant yields a different error: program main implicit none type t end type t type(t) :: b b = f_type_na() contains function f_type_na() type(t) :: f_type end function end program function f_type_na() 1 Error: Contained function 'f_type_na' at (1) has no IMPLICIT type c0.f90:11.6: b = f_type_na() 1 Error: Can't convert UNKNOWN to TYPE(t) at (1) Apparently we apply implicit typing to the INTERFACE version (although IMPLICIT NONE is given).
next prev parent reply other threads:[~2014-01-05 13:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-28 7:43 [Bug fortran/58557] New: " burnus at gcc dot gnu.org 2013-09-28 7:50 ` [Bug fortran/58557] " burnus at gcc dot gnu.org 2014-01-05 12:41 ` dominiq at lps dot ens.fr 2014-01-05 13:07 ` janus at gcc dot gnu.org [this message] 2014-01-05 13:39 ` janus 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-58557-4-7UlZfWlyaN@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).