public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56500] New: [OOP] "IMPLICIT CLASS(...)" wrongly rejected Date: Fri, 01 Mar 2013 18:07:00 -0000 [thread overview] Message-ID: <bug-56500-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56500 Bug #: 56500 Summary: [OOP] "IMPLICIT CLASS(...)" wrongly rejected Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org CC: janus@gcc.gnu.org Found at http://mailman.j3-fortran.org/pipermail/j3/2013-March/006167.html "IMPLICIT CLASS(...) (...)" does not properly work with gfortran. R560 implicit-stmt is IMPLICIT implicit-spec-list or IMPLICIT NONE R561 implicit-spec is declaration-type-spec ( letter-spec-list ) R403 declaration-type-spec is intrinsic-type-spec or TYPE ( intrinsic-type-spec ) or TYPE ( derived-type-spec ) or CLASS ( derived-type-spec ) or CLASS ( * ) Example by Reinhold Bader: module mod_upimp type :: foo integer :: i end type end module program upimp use mod_upimp implicit class(foo) (a-b) implicit class(*) (c) allocatable :: aaf, caf allocate(aaf, source=foo(2)) allocate(caf, source=foo(3)) select type (aaf) type is (foo) write(*,*) aaf end select select type (caf) type is (foo) write(*,*) caf end select end program
next reply other threads:[~2013-03-01 18:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-01 18:07 burnus at gcc dot gnu.org [this message] 2013-03-02 0:07 ` [Bug fortran/56500] " burnus at gcc dot gnu.org 2013-03-17 12:55 ` janus at gcc dot gnu.org 2013-03-17 13:12 ` janus at gcc dot gnu.org 2013-03-17 16:00 ` janus at gcc dot gnu.org 2013-03-17 19:46 ` dominiq at lps dot ens.fr 2013-03-17 21:02 ` janus at gcc dot gnu.org 2013-03-17 21:30 ` dominiq at lps dot ens.fr 2013-03-17 22:38 ` janus at gcc dot gnu.org 2013-03-18 12:17 ` dominiq at lps dot ens.fr 2013-03-18 12:57 ` janus at gcc dot gnu.org 2013-04-01 15:34 ` 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-56500-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).