It’s convention I think. It’s just one way of organizing your C++ files to make it more obvious. I believe they use public to represent includes (ie. header files that allow you to expose the signature of your classes to other files) and private being mostly implementation files (ie. files you wouldn’t want to use as includes). In some cases I’ve seen people not use public/private at all and go with their own set up.
1 Like