Re: True/False: As of VC 6.0, with MS compilers, usage of new(noth
"ultranet" wrote:
It built in Release, but not in Debug in that MFC project. Given that i
don't feel like messing w/ new macros, i think i'm making a rule for myself
to not use new(nothrow) in MFC projects. When those macros aren't defined,
i'll consider using it, but it appears it's all exacerbates by the lack of
standard compliance. I'll try to read the article mentioned in full, and see
if there are any better alternatives than b.
Reproduced it:
char* cArray = NULL;
try {
cArray = new char[3500000000];
cout << "array == " << (unsigned int)cArray << endl;
} catch(bad_alloc&) {
cerr << "bad_alloc" << endl;
}
cout << "Done!" << endl;
Getting 0.
OK, new rule for myself:
1. if code has potential for being cross-platform, use try-catch, and if
code is to be built w/ pre-.NET libraries for Windows, preferrably also check
for NULL, at least until VC .NET libraries are adopted for building.
2. if code is Windows-specific, and if code is to be built w/ pre-.NET
libraries for, preferrably, only check for NULL, at least until VC .NET
libraries are adopted for building.