Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!cunixd.cc.columbia.edu!jtt
From: jtt@cunixd.cc.columbia.edu (James T. Tanis)
Newsgroups: comp.lang.c++
Subject: Re: Base class access: by name only?
Message-ID: <1990Nov30.003722.22679@cunixf.cc.columbia.edu>
Date: 30 Nov 90 00:37:22 GMT
References: <59306@microsoft.UUCP> <1990Nov29.175741.116@Think.COM> <1990Nov29.224455.476@Neon.Stanford.EDU>
Sender: news@cunixf.cc.columbia.edu (The Daily News)
Organization: Columbia University
Lines: 11


I've used the shorthand method available on the Macintosh
(inherited::<method>) and it sure has made my life easier.

In particular, it makes inserting a new class into a _BIG_ heirarchy pretty
much a snap. Also, It would seem not to cause any more ambiguity than the
very existence of multiple inheritance does now.

I most definitely think it should be a candidate for inclusion in ANSI.

-JT


Brought to you by Super Global Mega Corp .com