Jump to content
Site Stability Read more... ×
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views

No Subject Here

Sign in to follow this  


Basic locking has been reintergrated into the library. This was the first thing up since the testing system actually depends on locking to some degree. Before it was implemented against do-nothing stubs. This is less hackish than it sounds since the do-nothing stubs are still in the library as the single threaded build policies. That is to say, depending on a build flag, the ClassLevelLockable template class will either create proper locks for a multi threaded build, or perform a bunch of no ops in a single threaded build.

Next up is probably some of the simpler utility classes. Right now some of the code is dependent on some basic stuff provided in boost and loki. There's no reason that functionality can't be reimplemented in my library. Not that there's anything wrong with using boost per se, but there's quite a bit a scaffolding that goes along with including any boost header, and one of the goals of the rework of my code library is to reduce compile times. loki isn't quite as heavy weight, but since I've ended up modding the headers quite a bit anyways, might as well reimplement them in my library.
Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!