Well,
There are multiple ways to go around about this. The way you are doing it is ok, thats how I use them sometimes. You could do something like:
// SomeClass.hstruct CSomeStruct{public: void myFunction(void); int myInteger;private: int hiddenInt;}class CSomeClass{public: CSomeStruct myStruct;};Then you could call on myFunction like: CSomeClass *myClass = new CSomeClass;myClass->myStruct.myInteger = 1;// or for a functionvoid CSomeStruct::myFunction(void) { myInteger = 5; hiddentInt = 3;}Remember, since myFunction is called within CSomeStruct, myInteger can be called directly from your function. Now you can not call hiddenInt outside of the class/structure, only functions inside can.You can also make a typedef struct to have extra variables attached. typedef struct { int variable;} extraVars;// add under public area in CSomeStructextraVars vars;// thenmyClass->myStruct.vars.variable = 5;// vars is extraVars and "variable" is inside the struct
It's usually a good idea to keep one header file with all the stuctures and classes inside. At least in my opinion. Then when you are ready to use them just include one .h file that holds all your structures, classes and typedef structs.
Also dont forget the:
#ifndef MYHEADER_H
#define MYHEADER_H
// code
#endif
In your header file.
Hope this all made sense,
[BDS]StackOverflow
[edited by - BlueDev on March 23, 2004 4:03:31 PM]
Simple question, let''s assume you have a container class setup something like the following:
