One header for multiple cpp files
I read this and I think that I understand the problems that may arise later. However, despite all this, I believe that my problem may be a special case, and I wonder if anyone has a VARIOUS offer.
I worked on the server and the client for a long time, and it was originally assumed that the all-encompassing CommandManager class became a terrible monster. It was designed to intercept messages received from possibly hundreds of clients, analyze it, determine what a team is and send it to the right function in the right class.
This is done by filtering the message after decoding the header, then by matching the "plain text" command received on std :: map, preloaded with all the commands.
This means that for every other team that I implement, I need a corresponding member function. It was originally originally .. but now I have more than 100 teams, and I'm not even close to that. I get to 4,000 lines of code in a .cpp file, and I am having problems tracking all of this. Despite having decent naming standards, this becomes a ploy for a lot of code that I would rather distribute.
I still consider myself a big newbie in programming in general and C ++.
Has anyone else encountered these problems in the past when developing a large project, and what did they do to fix these problems?