Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!uunet!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.std.c++
Subject: Re: Packing Across Inheritance Boundaries is Currently Allowed.
Message-ID: <1086@lupine.NCD.COM>
Date: 4 Aug 90 18:53:00 GMT
References: <1990Aug3.211414.23872@watmath.waterloo.edu>
Distribution: comp
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 21

In article <1990Aug3.211414.23872@watmath.waterloo.edu> gjditchfield@watmsg.uwaterloo.ca (Glen Ditchfield) writes:
>
>I think that packing of classes is allowed by the current definition of
>C++...

Of course it is ALLOWED.  Lots of things are allowed.  That's not the point.
The point is "What do the people who need inheritance-boundary packing to
ALWAYS occur (regardless of which compiler they are using) do?"

If you are trying to write portable code, and you need the kind of
packing that we are talking about, as of now you are out of luck because
the closest thing that we currently have to a "standard" is E&S which
does not specify a way to *force* this kind of packing to occur regardless
of which "conforming" implementation you are using.


-- 
// Ron Guilmette
// C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.