public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jilfa12 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51995] New: Polymorphic class fails at runtime Date: Wed, 25 Jan 2012 10:36:00 -0000 [thread overview] Message-ID: <bug-51995-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51995 Bug #: 51995 Summary: Polymorphic class fails at runtime Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: jilfa12@yahoo.com Created attachment 26458 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26458 A factory pattern design to illustrate class pointers (polymorphic) behavior The attached factory pattern compiled successfully. 1 PROGRAM main 2 3 USE factory_pattern 4 5 IMPLICIT NONE 6 7 TYPE(CFactory) :: factory 8 CLASS(Connection), POINTER :: db_connect => NULL() 9 10 CALL factory%init("Oracle") 11 db_connect => factory%create_connection() !! Create Oracle DB 12 CALL db_connect%description() 13 14 !! The same factory can be used to create different connections 15 CALL factory%init("MySQL") !! Create MySQL DB 16 17 !! 'connect' is a 'class' pointer. So can be used for either Oracle or MySQL 18 db_connect => factory%create_connection() 19 CALL db_connect%description() 20 21 CALL factory%finalize() ! Destroy the object 22 23 END PROGRAM main The test driver program above produced this error when compiled with gfortran-4.7.0: test_factory.f90:12.29: CALL db_connect%description() 1 Error: 'description' at (1) is not a member of the 'connection' structure test_factory.f90:19.29: CALL db_connect%description() 1 Error: 'description' at (1) is not a member of the 'connection' structure The program (according to http://fortranwiki.org/fortran/show/Factory+Pattern) apparently run successfully with gfortran-4.6.0. Is this a bug?
next reply other threads:[~2012-01-25 10:28 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 10:36 jilfa12 at yahoo dot com [this message] 2012-01-25 11:12 ` [Bug fortran/51995] " dominiq at lps dot ens.fr 2012-01-25 11:15 ` burnus at gcc dot gnu.org 2012-01-25 11:18 ` burnus at gcc dot gnu.org 2012-01-25 11:39 ` jilfa12 at yahoo dot com 2012-01-25 11:42 ` [Bug fortran/51995] [OOP] " burnus at gcc dot gnu.org 2012-01-25 11:43 ` jilfa12 at yahoo dot com 2012-01-25 13:10 ` burnus at gcc dot gnu.org 2012-01-25 13:34 ` burnus at gcc dot gnu.org 2012-01-25 14:09 ` jilfa12 at yahoo dot com 2012-01-25 18:19 ` burnus at gcc dot gnu.org 2012-01-25 18:26 ` burnus at gcc dot gnu.org 2012-01-25 19:25 ` dominiq at lps dot ens.fr 2012-01-25 20:34 ` dominiq at lps dot ens.fr 2012-01-25 23:18 ` burnus 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-51995-4@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).