You can also use working directories (. and ..) to reference directories in your hard drive, although it's generally a bad idea to keep headers in some arbitrary folder on your hard disk if they are user-created.
Basically you use it to declare functions and let the compiler know that they exist. That way you can call the functions in other files where the function isn't currently defined.
One trick with header files to avoid multiple inclusion errors is to encase the code inside preprocessor directives:
So if you press .help in the c++ game it would say What do u need and when u do .kick it would tell you to type in a name when u type in .kick <name> it kicks the player and says player kicked
I use Code::Blocks not VC++ but a header file (.h) contains prototypes, inline functions, macros, constants (i.e #define) and certainttypes of variables. When the IDE (i.e VC++) searches for include files it is usually in a default directory containing most, if not all, include files. If you have a corresponding (.cpp or .c++) file, it'd either be in the same directory or another - which varies among IDE configuration. Some IDE's and compilers allow you to transverse using a syntax such as (<../../header_file.h>). So a SUGGESTION would be to put your header files in the default directory and includ then via there. Also, to prevent inclusion, make sure you use the conditional preprossessor directives (i.e #ifndef HEADER_H etc...). If you decide to create and implement your own library(s) make sure it is under its own namespace. Last, you can always check out the HELP documentation for VC++ if all else fails; Microsoft usually has an exhaustive amount of documentation and even some tutorials for there products. Good luck my fellow Daniweb friend.
No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.