Re: [boost] object bloat using operators.hpp even with base chaining

From: William Ward (william.ward_at_[hidden])
Date: 2000-12-19 06:45:08

i've tried the explicit instantiation workaround, but i cannot get it
working for template classes,
i think this workaround is only for non template clases

This would probably get rid of the size increase if it could be used on
template classes.
If anyone has successfully implemented this, could they let me know,

thanks,
William Ward

----- Original Message -----
From: "Moore, Paul" <paul.moore_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Tuesday, December 19, 2000 11:37 AM
Subject: RE: [boost] object bloat using operators.hpp even with base chain
ing

> From: William Ward [mailto:william.ward_at_[hidden]]
> >  I'm having a problem with an increase in object size
> > when using the operators library from boost, using GCC
> > 2.95.2. I use single inheritence to derive from the Boost
> > classes using the base chaining technique described in
> > http://www.boost.org/libs/utility/operators.htm#chaining
> > as follows :
> [...]
> > I was wondering if there is any workaround for GCC to
> > remove this increase because in my application even a 4
> > byte penalty is unacceptable.
>
> I've not tried this, but would the explicit instantiation workaround for
> Borland noted in the document work here?
>
> Actually, are there any reasons why the Borland explicit instantiation
> technique is not suitable for general use? To be honest, it looks cleaner
> and more readable to me than the derivation version, either chained or
> not...
>
> Paul.
>
>
>