Typo Warnings (Windows Embedded CE 6.0)
1/5/2010
The Code Analysis tool reports typo warnings when it encounters problems in the syntax of your code.
For more information about Code Analysis warnings, see this Microsoft Web site.
The following warnings are reported in this category:
| Warning Number | Description |
|---|---|
C6031 |
Return value ignored: <function> could return unexpected value |
C6063 |
Missing string argument to <function> corresponding to conversion specifier <number> |
C6064 |
Missing integer argument to <function> corresponding to conversion specifier <number> |
C6066 |
Non-pointer passed as parameter <number> when pointer is required in call to <function> |
C6067 |
Parameter <number> in call to <function> must be the address of the string |
C6268 |
Incorrect order of operations: (<TYPE1>)(<TYPE2>)x + y. Possible missing parentheses in (<TYPE1>)((<TYPE2>)x + y) |
C6269 |
Possible incorrect order of operations: dereference ignored |
C6270 |
Missing float argument to <function>: add a float argument corresponding to conversion specifier <number> |
C6271 |
Extra argument passed to <function>: parameter <number> is not used by the format string |
C6272 |
Non-float passed as argument <number> when float is required in call to <function> |
C6273 |
Non-integer passed as parameter <number> when integer is required in call to <function>: if a pointer value is being passed, %p should be used |
C6274 |
Non-character passed as parameter <number> when character is required in call to <function> |
C6276 |
Cast between semantically different string types: char* to wchar_t*. Use of invalid string can lead to undefined behavior |
C6277 |
NULL application name with an unquoted path in call to <function>: results in a security vulnerability if the path contains spaces |
C6278 |
<variable> is allocated with array new [], but deleted with scalar delete. Destructors will not be called |
C6279 |
<variable> is allocated with scalar new, deleted with array delete [] |
C6280 |
<variable> is allocated with <function>, but deleted with <function> |
C6283 |
Allocation/free mismatch. |
C6284 |
<variable> is allocated with array new [], but deleted with scalar delete |
C6298 |
Object passed as parameter '%d' when string is required in call to <function>. |
C6299 |
Explicitly comparing a bit field to a Boolean type will yield unexpected results |
C6300 |
Explicitly comparing a bit field to a Boolean type will yield unexpected results |
C6302 |
Format string mismatch: wide character string passed as parameter <number> when character string is required in call to <function> |
C6303 |
Potential mismatch between sizeof and countof quantities |
C6306 |
Incorrect call to <function>: consider using <function> which accepts a va_list as an argument |
C6309 |
'realloc' may return null pointer: assigning a null pointer to <variable>, which is passed as an argument to 'realloc', will cause the original memory block to be leaked |
C6322 |
Empty _except block. |
C6323 |
Use of arithmetic operator on BOOL. |
C6324 |
Potential incorrect use of <function1>: Did you intend to use <function2>? |
C6325 |
Potential comparison of a constant with another constant |
C6326 |
warning C6327: Potential buffer overrun: SysAllocStringLen copies <number> characters from the string <variable> without validating the number of characters to copy. The code may crash |
C6327 |
Potential buffer overrun: SysAllocStringLen copies <number> characters from the string <variable> without validating the number of characters to copy. The code may crash |
C6328 |
<type> passed as parameter <number> when <type> is required in call to <function> |
C6381 |
Shutdown API <function> used with one of the following:
|
C6382 |
Shutdown resource ID <variable> used. |