This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Marking C++ new operator as malloc?
On Thu, 13 Sep 2007, Andrew Pinski wrote:
| On 13 Sep 2007 19:37:27 -0500, Gabriel Dos Reis <gdr@cs.tamu.edu> wrote:
| > Do you believe that allocator is prohibited by the C++ standard?
|
| Yes just because it points to another object at that point.
I'm afraid that is too dense for me. Please could you detail that
assertion?
| Now people do these tricks, I know but I guess most of them don't
| understand C++ that much to know they are invoking undefined behavior.
I don't think this is more about doing tricks that implementing than
implementing useful allocators. Surelly this kind of constructs does
not exist in C, but then C does not provide the appropriate apparatus
to write conforming alloctors.
Furthermore, ISO C++ is considering the addition of aligned_storage<T,N>.
http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2007/n2165.pdf
How do you reconcilie the above statement with the fact that an obejct
of type aligned_storage<T,N> will serve as (properly aligned) storage
for objects of type T?
-- Gaby