Jump to content
  • Advertisement
Sign in to follow this  
Duncanf

Making classes and structs visible globally across a whole project

This topic is 5166 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, I'm writing some code where some of the structs and classes I'm defining have to be visible to other files. For example, my Mesh class has to visible to my Utils.h/.cpp file because one of the functions takes in a Mesh object as an arguement (and obviously needs to know what a Mesh is). However, I dunno where to define the Mesh object to make it visible and usable across all files. I tried to define it in Mesh.h and include Mesh.h in the other files that need to use it, but I kept getting compiler errors saying class redefinition. Can someone tell me how they make their class and structure types usable across a whole project? Cheers, Duncan

Share this post


Link to post
Share on other sites
Advertisement
Looks like you need inclusion guards:


//mesh.h:

#ifndef MESH_H
#define MESH_H

class Mesh {
...
};

#endif




You should do it for every header file you create. Just take the name of the header, convert it to uppercase and use [smile]

Oxyd

Share this post


Link to post
Share on other sites
You need to do somethine like this in your Mesh.h file:

#ifndef _MESH_H_
#define _MESH_H_

// class definition goes here...

#endif


That should get rid of the class redefinition error.

Share this post


Link to post
Share on other sites
edit: oops! every body's posting at the same time? well here it is again-

If you declare mesh in a .h file, you'll want to put the preprocessor directives at the top and bottom of the file to prevent duplicate declarations.
a la:

#ifndef MY_MESH_HEADER
#define MY_MESH_HEADER

//your code here

#endif


What this does is:
checks to see if an arbitrary unique preprocessor label is defined (It shouldn't be for the first time). If it is not defined, then the compiler defines it and goes through your code. For subsequent #includes the compiler will see that the constant is already defined and will skip over your code.

Share this post


Link to post
Share on other sites
Cheers for the fast reply guys (means I won't have to remember what I was doing when I hit the bug for too long heh), #ifndef etc works a treat. Out of interest, how would I use this #pragma thing evolutional mentioned?

Share this post


Link to post
Share on other sites
Read this carefully: Organising code files

As for #pragma once, just add it to the beginning of your header file. You should still leave the include guards in though, #pragma once has been known to be buggy.

Share this post


Link to post
Share on other sites
Quote:
Original post by Fruny
You should still leave the include guards in though, #pragma once has been known to be buggy.


Especially when you consider the versions of GCC that flag it as being depreciated.

Share this post


Link to post
Share on other sites
Quote:
Original post by Duncanf
Cheers for the fast reply guys (means I won't have to remember what I was doing when I hit the bug for too long heh), #ifndef etc works a treat. Out of interest, how would I use this #pragma thing evolutional mentioned?


I beleive like this:

//mesh.h

#pragma once

class Mesh {
...
};


But the #pragma is compiler dependent (works on VC++ from certain version, IIRC). So I'd recommend you using the #ifndef thingy.

Oxyd

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!