Debug info (for all geeks)

[agnesgrussell]

I was browsing through the game files just checking if I could hack the starting money in the game and accidentially stumbled upon a build log.



I know most of the people won't care about these things but for me being a programmer myself it's pretty interesting to at least peak into how they did it.



So here goes. Things I discovered (in order of appearance):

They store all the code in D:\Compiler\code

They still use Microsoft Visual Studio 9.0 and not the new version

They use TortoiseSVN to commit files to the repository

They use C++ write it

The Windows user they use to build is called "mabuilder"

They still use Windows XP as the user path is "C:\Documents and Settings\mabuilder"

And demo was built on 07/16/2010 12:56:57, which is probably the most important bit of this file





There are also some TODO's, which I suspect are long fixed but still:

D:\Compiler\code\src\modules\SysCore/Core/C_Core.cpp(1918) : warning TODO: By Sobo: Remove this function and all references to it!

D:\Compiler\code\src\modules\SysCore/frames/C_Dummy.cpp(220) : warning TODO: neslo by sem dat ten alokator?

D:\Compiler\code\src\modules\SysUtils\HashName\C_H ashName.cpp(331) : warning TODO: Tables patching TU hack - remove later

D:\Compiler\code\src\modules\SysUtils\chunks\C_Inp utChunk.cpp(166) : warning TODO: check the value and perhaps lower the number

D:\Compiler\code\src\modules\SysInput/DirectX/C_InputDeviceDX.cpp(34) : warning TODO: podivat se na reserve, zere to asi 130 kilo

D:\Compiler\code\src\modules\SysMeshCD/Spatial/MeshCD/MeshCDOpcode/MeshCDSubdivOpcode.cpp(1342) : warning TODO: Mutex in C_MeshCDSubdivOpcode::Collide - performance impact expected, need to solve this asap





And last but not least, they've got some interesting header files, such as:

CompileShadersForPS3OnPC.h

CompileShaderForPS3.cpp

PS3SpecificFragments.h

I_ParamTableBasePS3.cpp

CompileShaderForPS3.cpp

C_DeviceShaderStatisticsPS3.cpp

C_DeviceConstantTablePS3.cpp

C_DeviceCompiledShaderPS3.cpp

etc

[IIOY]

If my husband was on this site, he would like this. :-)

[Deleted]

For which game?

[GilliC]

And this is part of the reason we have a strict no-TODO policy in our code. Any small refactoring must be complete pre-comit, and any larger tasks go into the backlog as technical debt.nits way too easy to overlook TODOs, and then you look like a tool when you realize years later that they're still not done!

[panicked]

Jun 20, 2014 21:54:41 GMT -5 GilliC said:

And this is part of the reason we have a strict no-TODO policy in our code. Any small refactoring must be complete pre-comit, and any larger tasks go into the backlog as technical debt.nits way too easy to overlook TODOs, and then you look like a tool when you realize years later that they're still not done!

I understood precisely none of this. Do I have to give my geek card back?

[GilliC]

Jun 22, 2014 9:02:02 GMT -5 panicked said:

Jun 20, 2014 21:54:41 GMT -5 GilliC said:

And this is part of the reason we have a strict no-TODO policy in our code. Any small refactoring must be complete pre-comit, and any larger tasks go into the backlog as technical debt.nits way too easy to overlook TODOs, and then you look like a tool when you realize years later that they're still not done!

I understood precisely none of this. Do I have to give my geek card back?

Well, there were some typos: "pre-commit" and "It's way too easy..."

And you'd only have to give back your software-engineering sub-card if you'd been claiming it.