From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-342853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 22069 invoked by alias); 9 Jan 2011 12:34:26 -0000
Received: (qmail 21937 invoked by uid 22791); 9 Jan 2011 12:34:26 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 09 Jan 2011 12:34:22 +0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46313] [OOP] class container naming collisions
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-46313-4-pWK8YbSu16@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46313-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46313-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Sun, 09 Jan 2011 12:42:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-01/txt/msg00792.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46313

--- Comment #25 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-01-09 12:34:08 UTC ---
(In reply to comment #24)
> r168610 contains the patch from comment #20 which fixes comment #19.
> 
> Is there anything left to do here, or should we finally close this one?

I think we might need to revisit the issue when submodules are implemented -
but until then everything should work - even the program below works - thus
closing as FIXED should be OK.

The following program has a name clash - but as the internal procedure is
internal, it does not leak out into global name space and works:

module mm
type t
end type t
end module mm

subroutine outer
call mm
contains
  subroutine mm
    type t
    end type t
    class(t),allocatable :: a2
    allocate( t :: a2)
  end subroutine mm
end 

use mm
class(t),allocatable :: a1
allocate( t :: a1)
call outer
end