From 8698009917524527833 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,db4807a3f0a1e742 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 1994-08-14 23:06:15 PST Path: bga.com!news.sprintlink.net!hookup!yeshua.marcam.com!MathWorks.Com!news2.near.net!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!andrew.cmu.edu!rr2b+ From: Robert Andrew Ryan Newsgroups: comp.std.c++ Subject: Re: Multiple inheritance and delete Date: Mon, 15 Aug 1994 01:37:41 -0400 Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA Lines: 16 Distribution: world Message-ID: References: <1994Aug14.181541.3096@corona.com> NNTP-Posting-Host: po2.andrew.cmu.edu In-Reply-To: <1994Aug14.181541.3096@corona.com> Excerpts from netnews.comp.std.c++: 14-Aug-94 Re: Multiple inheritance an.. Peter Kron@corona.com (1222) > The important compatibility issue is that standard C is still > accepted by the compiler. This is not exactly true. It is true that a large subset of C is accepted in C++. The exceptions primarily relate to the stricter type checking. (e.g. no assignment of ints to enums without an explicit cast, or is that illegal in C too :-), but also void * can't be assigned to foo *) Another sticking point is that some C++ compilers implement strict scoping of types. (ie, struct foo declared in a class A is only made visible as A::foo, not as plain foo which is noted as an anachronism in the ARM as I recall.) -Rob