AnsweredAssumed Answered

CCES behaviour inconsistent on undeclared functions

Question asked by MikeSmithCanada on Jul 25, 2013
Latest reply on Jul 26, 2013 by CraigG

Found the following

Hello world .cpp with deliberate errors to show CCES capability

 

write hellp.cpp

void main(void) {

     printf("Hellooooooo\n");   // note no <stout> declared

     SimpleFunction( );

}

 

Hover over SimpleFunction( ) -- CCES recognizes as undeclared function

Hover over printf( ) -- CCES recognizes as declared function and show prototype

 

Compile -- 3 errors -- undeclared printf, SimpleFunction, and a spelling mistake in Hellooooooo (you must be joking)

Hover over printf, SimpleFunction -- both now recognized as undeclared

 

Add #include "stdout.h" -- still undeclared printf -- I thought #include "file.h" should first look for local and then system file as a C and C++ requirement, is that enforced differently in CCES?

 

work with <stdio.h>

Outcomes