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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.182.19.164 with SMTP id g4mr5206177obe.42.1449675221303;
        Wed, 09 Dec 2015 07:33:41 -0800 (PST)
X-Received: by 10.182.120.164 with SMTP id ld4mr93135obb.14.1449675221282;
 Wed, 09 Dec 2015 07:33:41 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!feeder.erje.net!2.us.feeder.erje.net!enother.net!enother.net!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!mv3no13835509igc.0!news-out.google.com!l1ni1585igd.0!nntp.google.com!mv3no13835506igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Wed, 9 Dec 2015 07:33:41 -0800 (PST)
In-Reply-To: <n49b9t$41r$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=138.162.0.41;
 posting-account=9yqilwkAAAAlbxojEc6DW1OEOsACipCN
NNTP-Posting-Host: 138.162.0.41
References: <8bc7fd76-f00a-4eea-9715-470af028fc84@googlegroups.com>
 <1krm4xun4e4ny.jmh9kvf6s0a9.dlg@40tude.net>
 <12dc7aea-933d-4271-95bd-10df808917e4@googlegroups.com>
 <5hfb2q9imjfu.zs3xp9gxw0d3.dlg@40tude.net>
 <5788b259-8886-4ee2-8c3d-7799abfd840e@googlegroups.com>
 <rt3n7ox7u8lf$.1me9jljeld3bs$.dlg@40tude.net>
 <14acd8b0-a5e9-40fd-b7cc-d319f914d507@googlegroups.com>
 <n47n11$3tr$2@dont-email.me>
 <d674e44a-6341-4f73-903f-4bcee8406912@googlegroups.com>
 <25d385ff-a7c6-40e8-bee0-9e465f92d98b@googlegroups.com>
 <n49b9t$41r$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <99fe2106-3038-4513-bb67-5125618219ba@googlegroups.com>
Subject: Re: I'm facing an issue with: call to abstract procedure must be
 dispatching
From: Jere <jere.groups@gmail.com>
Injection-Date: Wed, 09 Dec 2015 15:33:41 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2623
X-Received-Body-CRC: 1987577517
Xref: news.eternal-september.org comp.lang.ada:28740
Date: 2015-12-09T07:33:41-08:00
List-Id: <comp.lang.ada>

On Wednesday, December 9, 2015 at 8:48:02 AM UTC-5, G.B. wrote:
> On 09.12.15 14:40, Jere wrote:
> > A class with only static members and static methods.
>=20
> A file will do, in both C++ and in C.
> Ada does not have file scope, but does
> have packages, so the names are full names.

In C that's really all one can do.  In C++ one prefers not to do it using f=
ile scope as that just pollutes the global namespace.  The preference is al=
ways to use either a namespace or class to wrap members and data.  Also, on=
e cannot get protected (c++ meaning) static methods or members using just f=
ile scope.  While that is somewhat limited in use, it does have its benefit=
s in some designs.  The big reason is not to put all of one's stuff into th=
e global namespace.  Then it ends up forcing one to leave behind some meani=
ngful names in order to not clash with another item of the same signature.

Regardless, the Ada package way is much cleaner and nicer.