Monday, December 3, 2018
Removing Boost
Why its problematic
Having boost in the project is a big help since it implements a huge range of useful features and objects. However over the years a lot of these features have been moved into the c++ standard library. Having boost included also makes building goblin camp a little harder across platforms. This lead us to start replacing the boost libraries with the std equivalent.The Move
Moving to std libraries most of the time isn't a problem since some features of boost are transferred into the standard. So for libraries likecstdint
it almost exactly the same as boost/cstdint
. To change it all that needs to be done is change the namespace and include statement to use the standard one. One pr after and we use one less boost library. I feel like most of these boost libraries won't be too hard to remove except for the one deeply ingrained in the project.
Subscribe to:
Posts (Atom)
-
Travis continued This pr addressed that after a lot of trial and error our travis.yml got quite out of hand. My job was to clean it up an...
-
The Basics If you're not familiar with stat I will give you a quick rundown. Stat is used in UNIX to view information about a file. In ...
-
Why its problematic Having boost in the project is a big help since it implements a huge range of useful features and objects. However over...