This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [libstdc++-v3] Remove std::construct and std::destroy
- To: Jason Merrill <jason_merrill at redhat dot com>
- Subject: Re: [libstdc++-v3] Remove std::construct and std::destroy
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Tue, 3 Jul 2001 12:59:57 -0700 (PDT)
- cc: stephen at bregmasoft dot com, libstdc++ at gcc dot gnu dot org
> IMO, code that used to work should continue to work where this is not too
> difficult to support. So I think the definitions should remain in the
> library subject to #ifndef __STRICT_ANSI__.
I disagree. This is why we have the backward include directory. I think
code that's not in the standard and from the original HP implementation
should either be removed, or put into backward.
Since removal appears to be controversial, perhaps the backward idea is
better.
I think the goal should be to have standards-conformant headers, and
older/deprecated headers available by request.
-benjamin