Two structures, bunch of programs.

[Peteris Krumins]

Hello,

What is the best method to do the following:

Let's say two programs use the same data structure. Each one of them keeps
all the function prototypes and other structures in header files.
Some functions have the same name but take different parameters, so i cant
include first programs header file in the second program (unless i #ifdef).

What is the best aproach to use the same data structure used by 2 or more
programs?
Put the structure used by both programs it in a seperate header file, so
if it changes i wouldnt have to change it in 2 or more sources?
Or use #ifdef .. #endif?

Or any other method?


P.Krumins

[Sam Zoghaib]

Peteris Krumins wrote in article
<Xns93BB13C4FC04Awhitesuneapollolv@130.133.1.4> on Thursday 17 July 2003
00:57 in comp.unix.programmer:

> What is the best aproach to use the same data structure used by 2 or more
> programs?
> Put the structure used by both programs it in a seperate header file, so
> if it changes i wouldnt have to change it in 2 or more sources?
> Or use #ifdef .. #endif?

It depends on how those 2 programs are separated; if they are (part of)
different projects, just put a copy of the header in each project, with the
necessary modifications.

If they are somewhat closely related (like, let's say, an
encryption/decryption pair) or belong to the same project, you may want to
have a single header where functions prototypes are between #ifdef...#endif

Anyway, try to keep the header simple. Even in the latter case, if having a
single header makes it hard to read, use 2.

Sam
--
"If sharing a thing in no way diminishes it, it is not rightly owned if it is
not shared."

- St Augustine

[Peteris Krumins]

Sam Zoghaib <NOsam@zep.homedns.orgSPAM> wrote in
news:bf4nal$4hs$1@news-reader3.wanadoo.fr:

> Peteris Krumins wrote in article
> <Xns93BB13C4FC04Awhitesuneapollolv@130.133.1.4> on Thursday 17 July
> 2003 00:57 in comp.unix.programmer:
>

>> What is the best aproach to use the same data structure used by 2 or
>> more
>> programs?
>> Put the structure used by both programs it in a seperate header
>> file, so
>> if it changes i wouldnt have to change it in 2 or more sources?
>> Or use #ifdef .. #endif?

>
> It depends on how those 2 programs are separated; if they are (part
> of) different projects, just put a copy of the header in each project,
> with the necessary modifications.
>
> If they are somewhat closely related (like, let's say, an
> encryption/decryption pair) or belong to the same project, you may
> want to have a single header where functions prototypes are between
> #ifdef...#endif
>
> Anyway, try to keep the header simple. Even in the latter case, if
> having a single header makes it hard to read, use 2.
>
> Sam

Thanks for the tips.


P.Krumins