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/46897] defined ASSIGNMENT(=) not used for derived type component Date: Sun, 12 Dec 2010 22:26:00 -0000 [thread overview] Message-ID: <bug-46897-4-W00ZQL0EGU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46897-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46897 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[OOP] Polymorphic type - |defined ASSIGNMENT(=) not |defined ASSIGNMENT(=) not |used for derived type |used |component --- Comment #2 from janus at gcc dot gnu.org 2010-12-12 22:25:52 UTC --- I think one can run into the same problem already without polymorphism: module m implicit none type component end type interface assignment(=) module procedure assign end interface type t type(component) :: foo end type contains subroutine assign(lhs,rhs) type(component), intent(out) :: lhs type(component), intent(in) :: rhs print *,'defined assignment called' end subroutine end module program main use m implicit none type(t) :: infant, newchild infant = newchild end
next prev parent reply other threads:[~2010-12-12 22:26 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-11 22:20 [Bug fortran/46897] New: [OOP] Polymorphic type - defined ASSIGNMENT(=) not used burnus at gcc dot gnu.org 2010-12-12 22:15 ` [Bug fortran/46897] " janus at gcc dot gnu.org 2010-12-12 22:26 ` janus at gcc dot gnu.org [this message] 2010-12-13 7:37 ` [Bug fortran/46897] defined ASSIGNMENT(=) not used for derived type component burnus at gcc dot gnu.org 2010-12-13 9:08 ` janus at gcc dot gnu.org 2010-12-13 9:28 ` [Bug fortran/46897] [OOP] type-bound defined ASSIGNMENT(=) not used for derived type component in intrinsic assign janus at gcc dot gnu.org 2010-12-13 15:17 ` damian at rouson dot net 2010-12-13 16:37 ` burnus at gcc dot gnu.org 2012-08-11 13:18 ` pault at gcc dot gnu.org 2012-12-01 8:01 ` pault at gcc dot gnu.org 2012-12-03 10:02 ` burnus at gcc dot gnu.org 2013-05-22 9:19 ` burnus at gcc dot gnu.org 2013-05-22 9:22 ` burnus at gcc dot gnu.org 2013-09-15 14:19 ` burnus at gcc dot gnu.org 2021-02-03 21:22 ` gronki at gmail dot com 2022-05-25 13:08 ` trnka at scm dot com
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-46897-4-W00ZQL0EGU@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).