If (p==NULL) {
FillMemory (LogMsg, sizeof (LogMsg), NULL);
Wsprintf (LogMsg, "failure!!!!! \ n ");
WriteMsg (__FILE__ and __LINE__, LogMsg);
throw NULL;
}
Good bosses, recently met such a logic, throw in vc6 null can play after the message code and then go down, but this paragraph on vs2015 shot message whether or not to continue, choose to continue after debugging will have no reaction,
Issue the following
1. Throw a null have this kind of writing?
2. Why in vc6 can then go on, but not in 2015?