custom routines and MSC++

[nexusone]

I have been getting back into programming after of being out of it for a few year's.
I want to seperate my routines into diffrent .cpp files and use my own .h files.

I am using the code from nehe site to setup the window and opengl setup code.
The problem I am having is passing a structure from my routine.


//mystuff.h

struct XYZ_BUFFER
{
float x;
float y;
float z;
int dir_x;
int dir_y;
int dir_z;
};
// end .h


// mystuff.c

#include "mystuff.h" //defines my structure.

XYZ_BUFFER Check_boundary( XYZ_BUFFER bc )
{
// check location of object
// change direction if needed
// code not shown but works when in main program.
return( bc )
}

What is the proper way to access from another my main.c program.
It works when I have it all in one file....

[MikeC]

What error message are you getting?

[EricK]

Just guessing, but I noticed that you passed bc by value. You might want to pass by reference:
XYZ_BUFFER Check_boundary( XYZ_BUFFER & bc )

[nexusone]

The error message is during linking...
LNK 2001 unresolved external symbol

here is how my routine is defined in my main.c program.

XYZ_BUFFER xyz_object[64];

XYZ_BUFFER Check_boundary(XYZ_BUFFER);

what is the correct way to call a routine
and pass a varible structure from another .c file.

[phlake]

this is a dumb question, but you're including "mystuff.h" in main.c, right?

and mystuff.h should have a prototype for the function you're calling in mystuff.c

[This message has been edited by phlake (edited 07-13-2000).]

[nexusone]

Originally posted by phlake:
this is a dumb question, but you're including "mystuff.h" in main.c, right?

and mystuff.h should have a prototype for the function you're calling in mystuff.c

[This message has been edited by phlake (edited 07-13-2000).]

Yea, I have the mystuff.h in both mystuff.c and main.c

[nexusone]

If anyone is interested I can zip the code and e-mail it to you...

I know it has to be something very simple!

[DFrey]

Is one file a .cpp and another .c? That can cause linker errors like that, if the call type isn't explicity indicated.

In your .h try
typedef struct
{
...
} XYZ_BUFFER;

Alternatively, in your .cpp
change references to XYZ_BUFFER to
'struct XYZ_BUFFER'.

Originally posted by Troy:
In your .h try
typedef struct
{
...
} XYZ_BUFFER;

Alternatively, in your .cpp
change references to XYZ_BUFFER to
'struct XYZ_BUFFER'.

Ooops... you can see my C background bias...
I notice that this isn't necessary for C++

So, the second part of phlake's 'dumb'
question still applies, does your
.h file include a function prototype?

XYZ_BUFFER Check_Boundary(XYZ_BUFFER bc);