Common Coding Bugs

From enfascination

Jump to: navigation, search
Line 10: Line 10:
 
*if it is for a specific static field, it could mean that I forgot "ClassName::" on initializing it
 
*if it is for a specific static field, it could mean that I forgot "ClassName::" on initializing it
 
*if a function is declared from another file but that file isn't included
 
*if a function is declared from another file but that file isn't included
 +
 +
/usr/libexec/gcc/path/ld: multiple definitions of symbol
 +
 +
*If there are too many copies of a file name in the makefile.
  
 
  020walker.cpp:311: error: a function-definition is not allowed here before '{' token
 
  020walker.cpp:311: error: a function-definition is not allowed here before '{' token
 
  020walker.cpp:332: error: expected `}' at end of input
 
  020walker.cpp:332: error: expected `}' at end of input
 
*Missing closing curly bracket on an if-statement
 
*Missing closing curly bracket on an if-statement

Revision as of 15:55, 16 June 2009

Note: these diagnoses will tend towards being too narrow, and may have solutions that are more general

C++

/usr/libexec/gcc/PATH/4.0.1/ld: Undefined symbols:
Something
collect2: ld returned 1 exit status
make: *** [program] Error 1
  • if it is for a whole class, it could mean that in an abstract class, I didn't set a function declaration to 0
  • if it is for a specific static field, it could mean that I forgot "ClassName::" on initializing it
  • if a function is declared from another file but that file isn't included
/usr/libexec/gcc/path/ld: multiple definitions of symbol
  • If there are too many copies of a file name in the makefile.
020walker.cpp:311: error: a function-definition is not allowed here before '{' token
020walker.cpp:332: error: expected `}' at end of input
  • Missing closing curly bracket on an if-statement