Hi -
Quote:
Shouldn't the file hye.h be named hye2.h?!?
|
Irrelevant - the problem is a link error. #including the wrong header would result in a compile error.
"hye2.c" is named perfectly appropriately (although I would #include "hye.h" in hye2.c).
My guess is the OP probably just wasn't linking in "hye2.o" (separate compilation) or "hye2.c" (single-step compile/link, as in my example).
IMHO .. PSM