This is the most clean, grokkable, readable C++ code I think I've ever read. I feel like most open source C++ projects I read in non-game spaces are just a complete mess of indecipherable syntax. Is this game code uniquely well written or am I often looking at the wrong codebases?
Simpsons Hit and Run source code (2003)
21–30 of 177 posts
Re: Simpsons Hit and Run source code (2003)
#2220 year old "leaked" code that was apparently previously leaked at some point but no one noticed the first time around. :) I really did love this game back in the day though.
It finally finished uploading on dial-up ;) Yea surprisingly fun game given the premise. Up until that game I thought he Simpson's lived in Illinois instead of Oregon
Re: Simpsons Hit and Run source code (2003)
#23Earlier quoted context omitted.
It finally finished uploading on dial-up ;) Yea surprisingly fun game given the premise. Up until that game I thought he Simpson's lived in Illinois instead of Oregon
Just upgrade to the 56k baud already. :) I still think Groening was trolling with his Oregon comment. It's still every Springfield in the US.
Re: Simpsons Hit and Run source code (2003)
#24Re: Simpsons Hit and Run source code (2003)
#25This is the most clean, grokkable, readable C++ code I think I've ever read. I feel like most open source C++ projects I read in non-game spaces are just a complete mess of indecipherable syntax. Is this game code uniquely well written or am I often looking at the wrong codebases?
[1] Unchecked assumptions everywhere, #ifdef with platform specific code everywhere, singletons everywhere. Only spent 5 minutes browsing the code, I'm sure there's more examples.
Re: Simpsons Hit and Run source code (2003)
#26Re: Simpsons Hit and Run source code (2003)
#27Re: Simpsons Hit and Run source code (2003)
#28Can anybody explain the existence of all*.cpp files which include other source files?
Re: Simpsons Hit and Run source code (2003)
#29[flagged]
Re: Simpsons Hit and Run source code (2003)
#30Classic