I've done the following at the moment:
{$IFDEF SU_HAVE_SOCKADDR_SA_LEN}
// #define su_len su_sa.sa_len <- unsupported for now
{$ELSE}
// #define su_len su_array[0] <- unsupported for now
{$ENDIF}
// #define su_family su_sa.sa_family
OK . You have avoided using macros but are loosing the access to "pseudo"
members su_len,su_family,su_port and su_scope_id. The DOCUMENTATION_ONLY
suggests that these members are documented parts of the interface. Also it
will be up to the user to figure out where to get su_len according to
SU_HAVE
On Thu, May 5, 2011 at 17:05, Ludo Brands wrote:
> OK . You have avoided using macros but are loosing the access to "pseudo"
> members su_len,su_family,su_port and su_scope_id. The DOCUMENTATION_ONLY
> suggests that these members are documented parts of the interface. Also it
> will be up to the
I guess DOCUMENTATION_ONLY is defined in an external tool such as doxygen.
Applications wouldn't define this. My point is that if the "pseudo" members
are documented, someone will soon or later use them. If this header
translation is for your personal
use only, then all is fine...
-Message
