Destructor

[Kragen Sitaker]

Peter <pcc at ecet.vtc.edu> writes:
> In other words: you can't write portable programs based on what a
> particular implementation does or does not do....  However, this is
> a very important issue for any language defined by a formal
> document. For example, the C++ standard ...  One must consult the
> standard to know what is and is not portable behavior.

My experience with C++ was that the standard (or, anyway, the draft
standard) was not very helpful for those who want to know what is and
is not portable behavior, because no implementation implemented the
standard correctly.  I heard a rumor that now, four years after the
standard was ratified, there might be a compiler that complies with it
--- is that true?