- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software: Code Composer Studio
CCS 7.3 upgrade to 8.3 fixes some Symbol resolve issues and causes other code analysis errors for (uartstdlib.c, uartstdio.c) that have never been a past problem even in CCS9.1.
The class fix was supposed to make public/class identifiers & names be resolved. Well symbol names resolve now but identifier class not defined causes other errors. Parsing then hick-ups inside the class identifier *.h file. It may be why the uartstd~.c errors are occurring further down the include list. What is missing from the include list for CLASS identifier to be defined? It seems like the name symbol CLASS causes the parser to think it requires ( ; ) after it.
#20 identifier "class" is undefined
class NexObject
{
public: /* methods */The code analysis via IDE defaults assumes uartstdlib.c has new issues, never in several versions of CCS has that occurred.
#110 expression preceding parentheses of apparent call must have (pointer-to-) function type // // Get the value from the varargs. // ui32Value = va_arg(vaArgP, uint32_t);
Syntax error: // // Get the value from the varargs. // ulValue = va_arg(arg, unsigned long);
Hi Ki,
After renaming *.h to *.hpp, then made a unique & separate class for the second public inheritance (below) seems to push the compiler C++ parse pointer upward. The (typedef) incomplete error seems to lead to all the other C++ parsing errors there after. The C file (nextion_ctrl.c) was calling a C++ public class function. So the C compiler had no reference from the index leading IDE to find the C++ public class being called. I also renamed public NexObject class NexGetObject believing some kind of class inheritance issue was causing C++ 59 parsing errors.
Do you know what is wrong with the typedef leading to C++ compiler parsing errors below it?
