From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3ed8984f81760f2e
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: Visibility Rules For Children
Date: 1998/10/27
Message-ID: <wccyaq2byus.fsf@world.std.com>#1/1
X-Deja-AN: 405385980
Sender: bobduff@world.std.com (Robert A Duff)
References: <m34sss6juk.fsf@mheaney.ni.net>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 1998-10-27T00:00:00+00:00
List-Id: <comp.lang.ada>

Matthew Heaney <matthew_heaney@acm.org> writes:

> What are the visibility rules for children?

They're pretty subtle.  Read 3.4, 7.3.1, and 12.something.

Your example looks legal to me.  There is a place immediately within the
immediate scope of the derived type, where I is visible; therefore, the
inherited I should also become visible.

- Bob
-- 
Change robert to bob to get my real email address.  Sorry.