Challenge Threadᆦ ᆦ ᆦ

[nemesis567]

So classes are normally defined within .h (header) files, the file that defines the class methods is the .lib (library) file (maybe?), and the file that actually makes use of the class members is the main.cpp source file (or I guess any of the source files? o.o)?

Then when you write up main.cpp, you would #include the .h file, and then continue to use the functions defined in the classes in the .h file which you included.

maybe something like that?


Anyways, when you do start using classes in your script, you use them by created objects that use the classes as templates for their "settings" (or i guess arguments), and objects pretty much act like names for groups of variables (or I guess primitives, which includes functions and whatnot).

And normally this would be useful, because you can have the class and its members all be defined in a separate file from the file you're using to do things, but since you can't reference other files with hlp2 .hps files, you might as well just make global functions/variables that are smartly named. Unless of course you want to apply a templates of attributes to multiple different things, in which case the use of classes would at least be the most readable option.

Yes, you include the .h file. The other file is a mere .cpp file that holds the same name as the header file. It will auto link to it. You only do that to avoid giving unwanted information to the client.

The header file has the class's interface with the function prototypes, the other .cpp file contains the function definitions and the last contains the source code.

Templates wouldn't be the right word, but it's something like that. A class describes the object's atributes and functions.