From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,MSGID_SHORT autolearn=no autolearn_force=no version=3.4.5-pre1 Date: 28 Dec 91 17:14:20 GMT From: mcsun!sun4nl!cwi.nl!guido@uunet.uu.net (Guido van Rossum) Subject: Re: Multiple Inheritance Message-ID: <4969@charon.cwi.nl> List-Id: bs@alice.att.com (Bjarne Stroustrup) writes: >MI in C++ and elsewhere isn't perfect and it isn't a panacea, but it works >and it makes some styles of programming noticeably more convenient and >less obscure. Naturally, it can also be overused and misused, but basically >it works. Point taken. However, I still worry about MI. When MI is *not* used, it still imposes an overhead -- there is a "delta" offset in the vtbl that is added to "this" each time a virtual function is called, but this delta can only ever be nonzero when MI is used. I feel that this is in direct conflict with the C++ philosophy that language features you don't use shouldn't cause overhead. I am also still looking for examples of the styles of programming that are aided by MI -- anyone got pointers? --Guido van Rossum, CWI, Amsterdam "You can't do that in horizontal mode."