That's an old debate, right? Some people say that C++ is the only way to go nowadays, while others say you can do everything in plain C without needing the object based thing from C++.
Announcement
Collapse
No announcement yet.
about Id Tech4
Collapse
X
-
Yeah the C/C++ issue isn't a problem.
I'm more curious as to what the engine will have to offer. Alot of features have already found their way into opensourced engines already, so I doubt you'd see alot of projects switching to the engine, but probably more of a "cobbling" of the features they like out of it into their own.
Comment
-
Originally posted by Irritant View PostYeah the C/C++ issue isn't a problem.
I'm more curious as to what the engine will have to offer. Alot of features have already found their way into opensourced engines already, so I doubt you'd see alot of projects switching to the engine, but probably more of a "cobbling" of the features they like out of it into their own.
Comment
-
Originally posted by xav1r View PostWell, probably devs will update id tech 4 with more modern features like like tesselation or whatever you spell that, remove the 60 fps cap it has by default, maybe work on the megatexture if it includes some of it. Theres room for lots of features to add.
Comment
-
Originally posted by xav1r View PostThat's an old debate, right? Some people say that C++ is the only way to go nowadays, while others say you can do everything in plain C without needing the object based thing from C++.
You can do a substantive portion of C++'s OO stuff in C, though you have some odd sharp edges when you do it. Many things aren't automatic like they are in C++. It actually requires more discipline to code it that way than with C++ and moreover you end up with something that may not be as fast as the C++ code in many cases.
You can code C++ code that is faster and easier to maintain than C, but it requires nearly as much discipline to code OO in C to do it.
The biggest complaint I have with C++ development in general is that many tend to over apply OO development. In C++, you should really, really only apply as much OO as is realistically needed for your project. Templates are fine, but you shouldn't make everything a template. Abstraction is fine, but you shouldn't be making tons and tons of wrapper classes that serve little purpose past data encapsulation unless you NEED the encapsulation. (In many, many situations, the dev absolutely did NOT need it.) There's tons of more examples.
Comment
Comment