I recently came across this text: Java Style Classes in C++, by the author of the Sauerbraten/Cube engine (who also seems to work for Crytek).
It's got me pretty excited.
Since over the last year or two I've been learning Java, I've been finding C++ more and more frustrating. Namely the fact that you usually have to have two separate files for each class, the .cpp and the header.
But this text describes a method of organising your code such that the classes can each live solely in their own header files (and all method implementations can be within the class). Wonderful!
The only obvious *POSSIBLE* problem with this approach seems to be the potential for large compile times. But it might not be so bad...
A new project I've started will use this approach. So I'll see how it goes.
Byes :)
It's got me pretty excited.
Since over the last year or two I've been learning Java, I've been finding C++ more and more frustrating. Namely the fact that you usually have to have two separate files for each class, the .cpp and the header.
But this text describes a method of organising your code such that the classes can each live solely in their own header files (and all method implementations can be within the class). Wonderful!
The only obvious *POSSIBLE* problem with this approach seems to be the potential for large compile times. But it might not be so bad...
A new project I've started will use this approach. So I'll see how it goes.
Byes :)
Calendar
