Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Thanks for the kind words! The source code could be greatly however (conception mistakes, too many singletons, half of the documentation is written in French...).
It's been a while since last release, but I'm still working on it time to time (migration from SFML 1.6 to 2.0 was a big change).
Doom 3 was written in the 2000's, C++ has evolved a lot since then. I don't only mean C++11, rather "modern C++" in general, as taught by Meyers, Sutter, and so on. One recognition was that "pure" OOP, like Java used it all the time, was too limited on its own. Alternative abstraction techniques, most notably templates, became interesting, and people began to combine different approaches. For example, the STL is extremely flexible, although the container classes don't use inheritance. Or std::function is the perfect example of type erasure, a combination of static and dynamic polymorphism. It is much more powerful than the pure OOP equivalents (observer/command pattern).
"In some ways, I still think the Quake 3 code is cleaner, as a final evolution of my C style, rather than the first iteration of my C++ style, but it may be more of a factor of the smaller total line count, or the fact that I haven’t really looked at it in a decade. I do think “good C++” is better than “good C” from a readability standpoint, all other things being equal.
I sort of meandered into C++ with Doom 3 – I was an experienced C programmer with OOP background from NeXT’s Objective-C, so I just started writing C++ without any proper study of usage and idiom. In retrospect, I very much wish I had read Effective C++ and some other material. A couple of the other programmers had prior C++ experience, but they mostly followed the stylistic choices I set.
I mistrusted templates for many years, and still use them with restraint, but I eventually decided I liked strong typing more than I disliked weird code in headers. The debate on STL is still ongoing here at Id, and gets a little spirited. Back when Doom 3 was started, using STL was almost certainly not a good call, but reasonable arguments can be made for it today, even in games.
I am a full const nazi nowadays, and I chide any programmer that doesn’t const every variable and parameter that can be.
The major evolution that is still going on for me is towards a more functional programming style, which involves unlearning a lot of old habits, and backing away from some OOP directions."
PS: Please, please, please don't put dots between acronyms, it's just not the way to go, i.e. S.F.M.L or O.O.P. or A.P.I., it's SFML, OOP and API - thanks!I just feel like changing it up a bit, it's just more entertaining to me; not sure why to be honest, haha. I guess I'll quit doing that.
Thanks for all the help guys I guess I have a lot of reading to do.
such a small, uncommented and not clean, regarding code design, example won't teach him much
it's a better code design to avoid polymorphism where ever possiblewould be saying to avoid O.O.P., would it not?
or better said, use it only when really needed and not as general formula.Doesn't that go for almost all techniques?
As I wrote previously, I'm still learning. I didn't know that global/static variables are so bad for good code design. I've written one module for global managing resources (based on static variables), so there's long way to go through for me Thanks for advice!