Using Enums to Replace #define's with Strongly-typed Variables

-

Comments

Post a Comment

Popular posts from this blog

Fixing Conan Lock Issues

-
I've been implementing Conan as our C++ package manager, and I had the following issue cause me a fair amount of grief over the last couple days: [MyPackageName] is locked by another concurrent conan process, wait... If not the case, quit, and do 'conan remove --locks'  You would be forgiven for thinking conan remove --locks should do the trick, but alas, it does not.  After finding hints on several Conan Github issues, I finally figured out that manually removing the package folders in one or both of the following places will alleviate the issue: Windows : C:\Users\username\.conan\data\packagename WSL/Linux : /home/username/.conan/data/packagename
Read more

Dude, Where's My Framework?

-
Image
You start out your day with a nice cup of coffee, and think, "Ah, greenfield project day...smooth sailing".  You fire up Visual Studio and create a new C# project.  "First things first, I need library X." you say.  "Wait, what the?"   The full error:  Package 'MyPackage 1.0.0.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net6.0'. This package may not be fully compatible with your project.   "Ok" you think, "That library is a bit older.  I'll go update the library project to .NET 6 to match my project.  But, where is .NET 6?     "Ok, what about my new project?  Just as a test, does the warning go away if I set it to an older .NET Framework?  Wait, where are the .NET Framework versions?...
Read more

Initialize With Care

-
Pointers are funny things.  They are one of the make or break concepts for beginners, and even years later, they can cause grief to experienced developers.  I am no exception.  Here is one such story: I was faced with a class which I wanted to refactor.  It can be simplified as follows: In the interest of breaking up the responsibilities, I added a couple of interfaces. The idea is that I can pass around smart pointers to these interfaces and begin to decouple portions of the code.  For example, I can inject them into classes that need them: However, I made a mistake.  I blame it on years of using boost::intrustive_ptr instead of std::shared_ptr, but enough excuses.  Let's see if you can spot it. Do you see it?  If so, give yourself 5 points.  If not, maybe after seeing the output: 'second' going out of scope... Destructor 'first' going out of scope... 'root' going out of scope... All done... Both shared pointers ( first & second ) are ...
Read more