Header Files (.h)

Hi I have question on header files. I know you can make your own header file i.e. # include “myfile .h”. How do I use it in a program dose it have to be in the same folder as all the other .h . I checked out the FAQ and they did explain much. I just downloaded allegro and want to try some game programming.
Mach
:confused:

>How do I use it in a program dose it have to be in the same folder as all the other .h
User defined headers should be in the same path as the source files calling them, or in some other agreed upon location. What you do is put your declarations in a header, include the header in the source, write a separate implementation file if the header has functions, and compile the implementation file, linking it with the driver:

Code:

---

/* header.h */
#ifndef FUNKSHUNHEADER
#define FUNKSHUNHEADER

void funkshun ( );

#endif

/* header.c */
#include "header.h"

void funkshun ( ) {
  /* Do something */
}

/* main.c */
#include "header.h"

int main ( ) {
  funkshun();

  return 0;
}

---

Code:

---

$ gcc -o main main.c header.c

---

And POOF! it all works. :)

>>it all works.
My turn for a nitpik: This:
void funkshun ( );
won't work for C89. You should be declaring functions with void if they don't require parameters:

Code:

---

void funkshun (void);

void funkshun (void)
{
  /* Stuff here */
}

---

>My turn for a nitpik: This:
Why is everyone always (nit)picking on me? :p

>won't work for C89.
Incorrect, it'll work just fine for C89. However, technically it eschews argument checking by saying the the number and type of arguments are unknown.

>You should be declaring functions with void if they don't require parameters:
Yea, I should. But knowing how things work and choosing my own style isn't quite the same as using a style out of ignorance, wouldn't you agree?

p.s. When I write something big, I'll follow the rules more closely to save problems later, but my usual quick and dirty style doesn't do any damage, and it's faster than adhering completely to the standard on every line. :)

>>Why is everyone always (nit)picking on me? :p
Why not? :p :D

>>it'll work just fine for C89.
OK, it will, but it ain't good practice. For those following the thread (if there is anyone!), here is why it's not good:

Code:

---

void foo( )
{
}
int main(void)
{
  foo();
  foo(11, 12, 13);
  return(0);
}

---

The compiler doesn't know how many arguments foo() takes, and therefore isn't required to complain about the two different uses of it in main(). Had it been declared void foo(void), the compiler would complain about the second call in main().

Some compilers will issue a warning with the above code, for example, Borland 5.5 says:

Code:

---

Call to function 'foo' with no prototype in function main

---

>>But knowing how things work and choosing my own style isn't quite the same as using a style out of ignorance, wouldn't you agree?
Maybe, but.... The code is safer with void in the definition, I wouldn't call that a choice of style. And, "knowing how things work" is what most people come here to learn, so showing them the correct way is always a good thing.

>>it's faster than adhering completely to the standard on every line. :)
Faster by 4 key presses, eh!

Anyway, enough picking on my part. :)

>OK, it will, but it ain't good practice.
I'm here to get a job done, not make sure I'm practicing goodness. ;)

>foo();
>foo(11, 12, 13);
This really assumes that the user programmer is a moron. I mean, if you see empty parens in a function prototype, you've got to be pretty dense to try and pass it arguments. :rolleyes:

>The code is safer with void in the definition
Naturally, safer is much better for projects larger than a few hundred lines. In those situations it's possible in theory to not be able to find the prototype, or the definition, and not bother to look it up because you "know" what parameters it takes.

>I wouldn't call that a choice of style.
Style is as style does. :D

>Faster by 4 key presses, eh!
Indeed! That's four punches at the keyboard that could be used for more productive things. :) Anyway, I meant faster in general, not just specific to not using void for function tags...but I digress. On to other matters!