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,899484222880ae7c
X-Google-Attributes: gid103376,public
From: eachus@spectre.mitre.org (Robert I. Eachus)
Subject: Re: preventing inheritance
Date: 1996/12/19
Message-ID: <EACHUS.96Dec19140037@spectre.mitre.org>#1/1
X-Deja-AN: 204981569
references: <32B22CDC.3FE4@bix.com> <32B5A234.947@watson.ibm.com>
 <32B640FC.D30@bix.com>
organization: The Mitre Corp., Bedford, MA.
newsgroups: comp.lang.ada
Date: 1996-12-19T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <32B85141.376A@bix.com> Tom Moran <tmoran@bix.com> writes:

  > 2) If MS in the future adds a way to implement Get_First_Character on
  > Multiline edit controls, it would become reasonable to move that routine
  > from Edit_Controls.Single_Line to Edit_Controls, leaving
  > Edit_Controls.Single_Line a bodyless package containing nothing but a
  > single type definition.  It would become yet another instance of "this
  > seemingly pointless complexity is here for historical reasons". 
  >   My difficulty is really an aesthetic one so perhaps the only solution
  > is to modify my aesthetic sensibilities. ;)

   There are two other solutions:

   1) Provide your own Get_First_Character for multiline edits.  Can
be done.

   2) Define Get_First_Character outside of Edit_Controls, or nested
in a Single_Line package.  This reflects the actual structure--an
operation on the parent that is not inherited.


--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...