From malcolm@brackley.nag.co.uk  Wed Apr 19 19:25:12 2000
Received: from brackley.nag.co.uk ([62.232.54.10])
	by dkuug.dk (8.9.2/8.9.2) with ESMTP id TAA24113
	for <SC22WG5@dkuug.dk>; Wed, 19 Apr 2000 19:25:06 +0200 (CEST)
	(envelope-from malcolm@brackley.nag.co.uk)
Received: (from malcolm@localhost)
	by brackley.nag.co.uk (8.9.2/8.9.2) id SAA06682
	for SC22WG5@dkuug.dk; Wed, 19 Apr 2000 18:26:25 +0100 (BST)
	(envelope-from malcolm)
From: Malcolm Cohen <malcolm@nag.co.uk>
Message-Id: <200004191726.SAA06682@brackley.nag.co.uk>
Subject: Re: (SC22WG5.1779) local name
To: SC22WG5@dkuug.dk
Date: Wed, 19 Apr 2000 18:26:25 +0100 (BST)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Kruyt, E. W. said:

>In X3J3/95-007R2 11.3.2 the terms name and local name are both used,

I'll maybe comment on this suggestion later.

>This came up to me by reading 4.4.2 Determination of derived types:
>Data entities in different scoping units also have the same type if they are
>declared with reference to different derived-type definitions that have the
>same name ...
>
>I guess this name is the local name.

You cannot say "local name" without saying where it is local to (at least
not without some confusion).  I certainly don't know which scoping unit
you mean.

Anyway, the name in question is the name in the relevant derived-type
definition, viz the actual name that appears in the text of the program
on the derived-type statement.

In another scoping unit, that derived type may have a different "local name"
by virtue of the renaming available on the USE statement.  However, that
does not change the name that appears in the derived-type definition.

Cheers,
-- 
...........................Malcolm Cohen, NAG Ltd., Oxford, U.K.
                           (malcolm@nag.co.uk)