This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/46313] [OOP] class container naming collisions
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 7 Jan 2011 13:41:26 +0000
- Subject: [Bug fortran/46313] [OOP] class container naming collisions
- Auto-submitted: auto-generated
- References: <bug-46313-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46313
--- Comment #22 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-01-07 13:41:17 UTC ---
(In reply to comment #20)
> This is easily fixed by putting the first letter of the derived type name in
> upper case:
[...]
(In reply to comment #21)
> even with the patch for PR 41580. However, the check in
> gfc_simplify_same_type_as [...]
> should have succeeded as the (declared) type of "a1" is not type compatible to
> "a2" - nor vice versa.
Seems to work with the patch from comment 20: The same_type_as is simplified to
.false.
(One could probably still construct ambiguity by making full-use of submodules
types defined in internal functions...)