Re: Defect report: [lex.key] and [lex.operators] contradict each other

From:

jdennett@acm.org (James Dennett)

Newsgroups:

comp.std.c++

Date:

Mon, 6 Aug 2007 16:11:39 GMT

Message-ID:

<kfHti.6390$Vk6.5726@newsfe07.phx>

James Kanze wrote:

On Aug 6, 1:17 am, Alberto Ganesh Barbati <AlbertoBarb...@libero.it>
wrote:

James Kanze ha scritto:

int main(){
void * memory = operator new(1000);
mytype* = new mytype;
}

It is worth noting that many of the suggested preprocessor
substitutions seem to assume that the programmer only uses the
second case.

And also that he doesn't use any placement new.

In fact there is a technique that I used a couple of times to replace
new, that works for placement new also:

#define new SetDebugInfo(__FILE__, __LINE__) ? 0 : new

Sure, it doesn't work in every context where you can use "new", but it
never failed me in real-life code.

Not even in multi-threaded code:-)?

In multi-threaded code, one might assume that SetDebugInfo
would use thread-local storage; such techniques are one
argument for including TLS in standard C++0x once thread
support is added.

-- James

---
[ comp.std.c++ is moderated. To submit articles, try just posting with ]
[ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ]
[ --- Please see the FAQ before posting. --- ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html ]