Boost logo

Boost :

From: rwgk (rwgk_at_[hidden])
Date: 2002-03-06 21:59:30

--- In boost_at_y..., "David Abrahams" <david.abrahams_at_r...> wrote:
> Checking whether the destructor is trivial is the wrong check:
> int destroyed;
> struct X
> {
> X::~X() { ++destroyed; }
> };

??? Would this ~X qualify as a trivial destructor?
What I had in mind is:

    X::~X() {}

Either user defined or supplied by the compiler (and of course, all
types that X inherits from directly or indirectly also have to have a
constructor that "does nothing.")

It seems to me that our "Enhanced POD" idea is very similar, just
seen from a different angle.

> Well, that's what I was referring to in my previous message (and the
> sanity of the implementor has never been a consideration ;-P),

This makes (keeps!) the language very unwieldy for people that find it
necessary to implement their own containers (like myself). You cannot
assume that the standard provides everything anybody could ever need.

> I don't see what type traits have to do with it.

Same argument: IMO the language should provide /portable/ means
for implementing efficient containers.
At the moment it looks to me that type traits are involved one
way or another: in my proposal they are used for safety checks,
in your proposal you also seem to rely on the availability of
type traits:

You wrote:
> > It could, but it would require that the container
> > implementor specialize the constructors for the case where
> > the container's value_type is POD and the Iterator's
> > value_type is uninitialized.

> > vector(size_t n, uninitialized);
> >
> > (where uninitialized is a typename) is much more intuitive.
> That's not legal syntax. You can't pass a typename as a function
> argument.

This is the declaration of the constructor and it definitely works
for my array family.

> I think you're viewing it from the wrong angle. The way I see it,
> using a a conversion from uninitialized to complex<> when U ==
> uninitialized. That just happens not to initialize the members.

Your view has some elegance, but then each type needs to
know how it is constructed from the type uninitialized. How
could that work for types in, e.g. proprietary libraries
that I cannot change? You "delocalize" the problem of
"initializing a container" in the sense that the designer
of a user-defined type has to consider what happens when
his type is used as the value type of a container. To me it
seems much more desirable that the container adjusts to the
value-type rather than vice versa.

> Ultimately, I don't think you can/should locate the smarts in the
> vector.

Our views seem to be orthogonal...

> The right place to locate information about whether X can be
> in a particular way is in X, preferably in a constructor.

Again, this implies that any user-defined type has to be
made "container compatible." This idea makes me shudder,
especially since the alternative seems so obvious to me. My
experience also shows that it works well in practice.



> > P.S.: In some sense this issue is more pressing than the
> > complex<T> question: complex<T> mostly works OK, there is
> > just no promise that it will work on new platforms.
> ??? of course there is - the standard makes all kinds of promises
> it will work
> But aren't you still dissatisfied with all of the issues of layout?

That exactly is the point: all implementations known to me
provide the desired layout (i.e. "work OK") even though the
standard does not give a guarantee for this.

Boost list run by bdawes at, gregod at, cpdaniel at, john at