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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,7ee10ec601726fbf
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-10-16 12:39:12 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!arclight.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail
From: Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov>
Newsgroups: comp.lang.ada
Subject: Re: why not
Date: 16 Oct 2001 15:25:40 -0400
Organization: NASA Goddard Space Flight Center
Message-ID: <upu7ns7yj.fsf@gsfc.nasa.gov>
References: <Xns9133DBAF0AD71ralphworkcoza@196.25.240.158>
 <Sjlw7.37140$GT3.4946134@news2-win.server.ntlworld.com>
 <3BC30674.BA88AAB6@brighton.ac.uk> <9pvv3t$ves$1@news.huji.ac.il>
 <Bggx7.314$KN5.148429887@newssvr11.news.prodigy.com>
 <3BC5D730.DA950CC7@boeing.com> <9q4pa7$1ad$1@nh.pace.co.uk>
 <slrn9sdahp.k4.lutz@taranis.iks-jena.de> <3BC6ACC8.23EF21BC@free.fr>
 <QQCx7.26073$ev2.34583@www.newsranger.com> <3BC71F54.1FFE78FA@boeing.com>
 <1KGx7.26476$ev2.35117@www.newsranger.com> <3BC7AD82.2A0CCCD4@acm.org>
 <usncjtzix.fsf@gsfc.nasa.gov> <ERYy7.31400$ev2.37845@www.newsranger.com>
NNTP-Posting-Host: anarres.gsfc.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: skates.gsfc.nasa.gov 1003260451 4249 128.183.220.71 (16 Oct 2001
 19:27:31 GMT)
X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov
NNTP-Posting-Date: 16 Oct 2001 19:27:31 GMT
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
Xref: archiver1.google.com comp.lang.ada:14737
Date: 2001-10-16T19:27:31+00:00
List-Id: <comp.lang.ada>

Ted Dennison<dennison@telepath.com> writes:

> In article <usncjtzix.fsf@gsfc.nasa.gov>, Stephen Leake says...
> >
> >that C++ doesn't. C++ has no limited types, it has no distinction
> 
> Your point is quite valid, but this statement is not preciecly true. You can put
> the copy constructor in the "private" part of a class to achieve the same
> effect. They don't call it "limited", but its effectively the same thing.

True. 

Which raises the question; can the containers in the STL be used with
such "limited" types? I suspect not.

And I _always_ forget to hide the constructor on child types, when I
am forced to write C++ :).

-- 
-- Stephe