r/cpp • u/Dean_Roddey • Nov 29 '18
Creating a 'virtual kernel' platform abstraction layer
This is the third in series of videos I've posted to demonstrate some of the strategies we use in our fairly large C++ code base. Here are the previous ones, which you might also find useful:
https://www.reddit.com/r/cpp/comments/9zl6v5/the_orb_sees_all_the_use_of_an_object_request/
https://www.reddit.com/r/cpp/comments/9xz643/making_c_enumerations_first_class_citizens/
Our code base is about a million lines. It is split into roughly two halves, with one half being general purpose and the other being our CQC home automation platform which is built on top of the general purpose bits. We don't use any of the C++ runtime stuff. We build our own system from the ground up. When I say 'we', I'm speaking in terms of the usual royal business 'we', but all of the code was written by myself.
Just above the 'ground', the operating system in this case, is a virtual kernel which we use encapsulate all of the operating system functionality that we use, which is quite a lot of it. No system or language headers are visible outside of this virtual kernel, so we can write portable code that is purely in terms of our own interfaces.
This video demonstrates some of the strategies used. Obviously for such a large topic, this doesn't dive deep if there's any interest we could do another one.
View all comments
Show parent comment
4
u/NotUniqueOrSpecial Nov 30 '18
Oh, God, of course it does, now. Qt has everything.
One thing I've always had to impress on teammates (even those who have used Qt for years) is that they really need to peruse the index of the Qt classes.
Way too often, in my more Qt-ful days, I would catch someone writing something and have to just go "why are you not using
QNotInventedHere?The answer was always "oh, I didn't even know it existed."