Jump to content
  • Advertisement


  • Content Count

  • Joined

  • Last visited

Community Reputation

356 Neutral

About Sova

  • Rank
  1. Sova

    c# book recommendations

    C# and the .NET Framework is the best book on C# I've read. Note that some of the new C# features covered in the latest edition (and one before that) are unavailable in Unity.
  2. You're the boss of your project directory structure! It is what you say it is, and therefore there are no assumptions made. If you insist on future-proofing, you can define a variable in the top-level CMakeLists.txt that would hold the include directory for library. Then use it in another_library CMakeList.txt. Do whatever makes the overall structure clearer to you. I have no opinion either way. On Linux: probaby under /usr/shared/app or /usr/local/shared/app. On Windows: in the installation directory. I haven't the foggiest about OSX. HTH
  3. Generally, you shouldn't mix runtimes. That is, it is not safe to use a library that has been linked with a MSVCRT (MS Visual C Runtime) version other then the one you're linking with yourself. And each release of VS has its own version of runtime.   If a library doesn't provide a binary version linked with your runtime, you have no choice but to build the library yourself.
  4. Sova

    Adding new RAM, is a format required?

    There should be an option in the BIOS to disable automatic overclocking.
  5. Sova

    Adding new RAM, is a format required?

    Here are the limitations on physical memory for Windows systems. If you have Win8 or Win7 Professional or higher you'll be fine.
  6. Sova

    C If Statement Question

    Huh! I didn't know that. Thanks for the correction.
  7. Sova

    C If Statement Question

    This is just a nitpick, but I believe that `int main(int argc, const char * argv[])` is, in fact, not a valid signature for `main` function. Standard sayeth `int main(void)`, `int main(int argc, char* argv[])` or equivalent.
  8. OT   Out of curiousity, why did you decide to switch from LuaBridge to luabind?
  9. There is also Crystal Space which, together with its sister projects, might be worth checking out.
  10. Sova

    Maintaining a code library

    I think that Mercurial should be mentioned too. You can read all about it here.   Both work on the same principle, but Mercurial (or simply hg) is considered more newbie friendly then Git. It has simpler interface with fewer options that "do the right thing".
  11. Why not make it a parameter of `ModelCache`'s constructor?
  12. C++11 smart pointers are thread-safe. So sayeth the Standard.
  13. I don't understand this strategy. Why weak_ptr? The users will have to lock and check for expiration everytime using the asset. If you already have shared_ptr in the manager, why not for the users?   Because they're users. Giving out only weak_ptr's opens up the possibility to, f.ex. unload some resources that aren't actually being used in favor of some other high priority resources. This would need some mechnanism to avoid thrashing, tho. If you used shared_ptr instead, you wouldn't have the possibility to track actual usage.
  14. I disagree.   Having a shared_ptr in asset manager and handing out weak_ptr to asset users is a solid strategy.
  • 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!