Ok... so there's data isolation between differently named copies of the same class.
But what about same name copies in different contexts?
Or is this what inheritance is about? I can create sort of a master class and then create classes from that to do the actual work.Code:// in 1. cpp YourClass Fred; // in 2.cpp YourClass Fred;
The reason I keep pushing this point is that I actually do have something of an application in mind for it. Basically I will need to have a single list of information that will be used in differing parts of the program... but they all have to access that one single array of structs, updating it "on the fly"... I'm pretty sure I know how to do this in C, using a global array... but I would like to take a pop at it in C++ fairly early in the learning curve (to help me decide whether to continue working on it in C or not).