On Apr 30, 7:13 pm, xu****wei <xu****we...@[EMAIL PROTECTED]
> wrote:
> I don't think we need to override the DEFAULT operator new/delete.
> This makes your code doesn't work well together 3rdparty code (if it
> also override them).
>
> I suggest ISO C++ cancel this feature, just like we can't override
> operator+ of all C types. That is:
Practically, there's no way this will happen, as lots of existing code
makes use of this feature. If you think there's a problem, put your
effort into finding a way of structuring the resolution of memory
requests to avoid the issues you're experiencing, and if other people
see the merits, you might get it into a later C++ standard. Simply
banning everything is about as practical as asking the UN to make it
illegal for 3rd party libraries to include thread-unsafe code, or
requiring all libraries to be in namespaces registered with a global
body....
Tony
--
[ See http://www.gotw.ca/resources/clcm.htm
for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]
|
