Originally posted by Myrtl
Honestly someone please explain to me how people can understand this stuff.
I will (though this question probably was rhetorical

), by the example of two lines. I don\'t take responsibility if anybody uses this info and loses their job in case I messed up something, though!

C++ ./out/linuxx86/optimize/src/server/gem.o src/server/gem.cpp: In member function `void gemActor:: DoDamage(gemActor*, float)\':
This is the line that tells where the error(s) occured.
\"C++\" is the program that found the error, the compiler in this case.
\"./out/linuxx86/optimize/src/server/gem.o\" is the file that was about to be generated when the error(s) occured, an object file called \"gem.o\" in this case.
\"src/server/gem.cpp\" is the file that tries to use the offending code, the c++ source file called \"gem.cpp\" in this case.
\"In member function `void gemActor:: DoDamage(gemActor*, float)\'\" is where in this file the error(s) occured. In this case, inside a member function called \"DoDamage\" of the class called \"gemActor\", that returns nothing (void) and takes two arguments, one being a pointer to an instance of the class gemActor ( indicated as \"gemActor*\" ) and a floating point value, ( indicated as \"float\" ).
src/server/gem.cpp:1297: warning: converting to `int\' from `float\'
This is the line that tells where exactly an error occured and what the error is:
\"src/server/gem.cpp\" is the filename the offending code is actually located in (which may differ from the location of it\'s usage, which most commonly happens if the error is in a header file), in this case the same file, \"gem.cpp\".
\"1297\" is the line number at which the error occured.
\"warning\" is the severety level of the error, in this case it\'s just a warning that something that is not desired may be happening.
\"converting to `int\' from `float\'\" is what is happening, in this case there is an implicit conversion of a floating point value to an integer value.
This can be a good start for a debugging session as it often actually points to the location the error actually is.
Questions?

Anyway, I wouldn\'t bother trying to build it with CB being
that close.

@ Acraig: what\'s wrong with the current site (except that it might be a tad out of date)? Granted, it isn\'t the most flashy sort of thing, but OTOH it works with pure HTML (except the evil flash intro!), and also doesn\'t look bad, so...