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,555956c1cdd22308
X-Google-Attributes: gid103376,public
From: dennison@telepath.com
Subject: Re: Help - Constructors - ASAP.
Date: 1998/07/27
Message-ID: <6pi4jq$j73$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 375309061
References: <6p75qi$rcj@news.latnet.lv> <m3lnpg7j5s.fsf@mheaney.ni.net>
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Mon Jul 27 14:59:06 1998 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.0; Windows NT; Gateway2000)
Date: 1998-07-27T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <m3lnpg7j5s.fsf@mheaney.ni.net>,
  Matthew Heaney <matthew_heaney@acm.org> wrote:
> If the return type is tagged, then do NOT return the specific type as
> the return type of the function.  Either return the classwide type, or
> declare the constructors in a nested package called Constructors.  This
> way, the functions won't be primitive operations for the type, and
> therefore won't be inherited during derivation.

Hmm. You have probably been through this more than I, but it would think it
would be useful in some circumstances to have the function be inheritable. If
you need a new version of the "constructor" for a new derived type, you can
override the old one and the client won't be able to call the old one anymore.
If you make the original "constructor" class-wide instead, clients will always
be able to call it with any derived type.

T.E.D.

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum