Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!nsc!voder!decvax!roger
From: roger@decvax.UUCP (Roger H. Scott)
Newsgroups: comp.lang.c++
Subject: Re: problems in cfront 2.0 with +e[0|1] options and __ptbl__...
Keywords: cfront 2.0, virtual, pure virtual, __ptbl, __vtbl, bug/feature?
Message-ID: <72@pascal.decvax.UUCP>
Date: 19 Jan 90 20:08:36 GMT
References: <1379@mit-amt.MEDIA.MIT.EDU>
Reply-To: roger@procase.UUCP (Roger H. Scott)
Organization: proCASE Corporation, Santa Clara, CA
Lines: 8

A lot of work has gone into 2.0 cfront to reduce or eliminate redundant
vtbls.  Unless you are doing something *very* strange, it is quite likely
that playing silly games with +e options [one of the biggest crocks to
come along in a long time] will not buy you anything under 2.0.  The only
caveat is to make sure that each class that adds or redefines a virtual
function defines at least one of those functions *non*-inline.  I suggest
you try building your whole system without any +e use and see how you like
the result.