RE: [Doxygen-users] Typedef Aliases Don't Work

[Stephen G. <ste...@cl...>]

Couldn't you get the same result in your code by dropping the typedef
completely, leaving the latest version of the struct with the name 'Data' and,
when a new field is added, copying the existing 'struct Data', naming the copy
'struct Data<insert version number here>' and finally adding the new field to
'Data'?

Then Doxygen will work fine as-is, your code will work fine with only a couple
of changes in the header. The only difference would be that, at the moment, you
can refer to the latest version by two different names, so if you make use of
that fact then ignore this suggestion.

Regards,
Stephen Goudge


-----Original Message-----
From: dox...@li...
[mailto:dox...@li...]On Behalf Of Scott Palmer
Sent: 08 June 2001 02:43
To: dox...@li...
Subject: Re: [Doxygen-users] Typedef Aliases Don't Work

<snip>

I have a header file that keeps a typedef defined as the 'latest version' of a
struct that may evolve.  The older legacy structs will still be available in the
header but they will be undocumented.

e.g.

struct Data1
{
  int x;
};

// latest version of 'Data'
struct Data2
{
 int x;
 int addedMember; // new feature needs new data
};

typedef Data2 Data;

So recompiling withthe latest headers will always use the latest structs without
changing the source.

Scott