[Bug fortran/44917] [OOP] Detect ambiguous specifics in a generic TBP interface

2016-11-16 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44917 janus at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |4.6.0

[Bug fortran/44917] [OOP] Detect ambiguous specifics in a generic TBP interface

2010-10-30 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44917 --- Comment #3 from janus at gcc dot gnu.org 2010-10-30 13:52:44 UTC --- Author: janus Date: Sat Oct 30 13:52:39 2010 New Revision: 166089 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=166089 Log: 2010-10-30 Janus Weil ja...@gcc.gnu.org

[Bug fortran/44917] [OOP] Detect ambiguous specifics in a generic TBP interface

2010-10-30 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44917 janus at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug fortran/44917] [OOP] Detect ambiguous specifics in a generic TBP interface

2010-07-12 Thread janus at gcc dot gnu dot org
--- Comment #1 from janus at gcc dot gnu dot org 2010-07-12 08:59 --- Reduced version: module m type :: t1 integer :: i = 42 contains procedure, pass :: make_integer generic, public :: extract = make_integer end type t1 type, extends(t1) :: t2 integer :: j =

[Bug fortran/44917] [OOP] Detect ambiguous specifics in a generic TBP interface

2010-07-12 Thread janus at gcc dot gnu dot org
--- Comment #2 from janus at gcc dot gnu dot org 2010-07-12 09:02 --- Note that the ambiguity is detected if both specifics are already defined in the base class: module m type :: t1 integer :: i = 42 contains procedure, pass :: make_integer procedure, pass ::