V668 There is no sense in testing the 'destination' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. notepad_plus.cpp 1170
V668 There is no sense in testing the '_pShortcutMapper' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. nppbigswitch.cpp 1340
V668 There is no sense in testing the 'mEscCharSetProber' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. nsuniversaldetector.cpp 199
V668 There is no sense in testing the 'buffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 109
V668 There is no sense in testing the 'attrib' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 542
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 637
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 771
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 923
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 950
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 1011
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxml.cpp 1038
V668 There is no sense in testing the 'buffer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 113
V668 There is no sense in testing the 'attrib' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 546
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 641
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 845
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 997
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 1024
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 1085
V668 There is no sense in testing the 'clone' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmla.cpp 1112
V668 There is no sense in testing the 'returnNode' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmlparser.cpp 559
V668 There is no sense in testing the 'attrib' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmlparser.cpp 766
V668 There is no sense in testing the 'textNode' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmlparser.cpp 812
V668 There is no sense in testing the 'returnNode' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmlparsera.cpp 578
V668 There is no sense in testing the 'attrib' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmlparsera.cpp 785
V668 There is no sense in testing the 'textNode' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. tinyxmlparsera.cpp 831
V668 There is no sense in testing the 'pszUCS2' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. uniconversion.cpp 93
V668 There is no sense in testing the 'pszUCS2' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error. uniconversion.cpp 122