Well the answer is in your first line :) In an ATL program I'm locked into msvc already anyway, so I figure 'why bother'. This is of course only in Windows programs, not for anything I write that should be portable.There's no saving you is there? In C++ is new fails it is meant to throw bad_alloc. malloc doesn't throw anything.
Haha no there isn't :) To be fair, I'm just playing devil's advocate here: normally I'm the first one to tell people to use boost, exceptions, templates and all other goodies that C++ gave us. The original example was just an illustration of the problem - I don't want to use malloc, new, or any other manual memory allocation at all! I want the library to do it for me, and I don't care how it does it.
cheers,
roel
PS no matter how much I like pointless discussions like this ;) , I have some work to get done, so this'll have to be my last response to this thread, unless useful unicode things show up (which was what started the whole thing).
