Today marks a historic day for Twisted Pair, as we release the full source code to the Shock C++ Cross-Platform library.
The project files and Socket module are currently missing.
When I get time, I’ll take a day to create the project files for MSVC, Eclipse and XCode.
Look out for PyGLy, our Python graphics library, on GitHub soon.
Cross-platform abstraction is generally done with inheritance. I’ve developed a cleaner method that ditches inheritance but may turn some “purists” off.
There are many different methods programmers have picked up for laying out a C++ project or library.
After a number of years of implementing, interacting and improving C++ projects, I’ve found the following to be the best structure to use.
These design rules and patterns are designed to increase consistency, readability, modularity and reduce programmer error.
Tribute to the refinement of my coding style and practices goes to a number of people I’ve worked with (read: leached their brains), including but not limited to David Hogan, Jeremy Kincaid, et al.
Last updated 2011/02/16
I wrote about this issue a while ago, but the post was, well… a bit of a rant.
I’ve spent the last 5 years designing my C++ library Shock. It’s basically designed to let me create a number of games I’ve always wanted to make with a massive amount of code re-use and a number of other niceties thrown in.
I’ve been experimenting with Python and it’s opened my eyes to the flexibility of modern programming languages. I think it’s what I should be developing in.
I’ve coded C++ since uni. It’s what I do for a living. But the irony is, I hate C++. It’s not just that I work with it all the time and have had bad experiences, C++ is truly horrible. And the sad thing is, it’s so pervasive that we can’t shake it.
Twisted Pair Development 