[libannodex-dev] C++ clients and the use of 'class'asstructmember names.

[Silvia.Pfeiffer at csiro.au]

It's been done (and committed last Friday) for libcmml. Since it's been an API change, it's received a new version number and I'l lbe doing another release.

Conrad and I have discussed how to fix it for libannodex - we want it to be backwards compatible with previous versions of libcmml, so will put a configure option in. Watch this space...

Cheers,
Silvia.


-----Original Message-----
From:	libannodex-dev-bounces at lists.annodex.net on behalf of Jamie Wilkinson
Sent:	Sat 3/11/2006 10:11 AM
To:	libannodex-dev at lists.annodex.net
Cc:	
Subject:	Re: [libannodex-dev] C++ clients and the use of 'class'asstructmember names.

This one time, at band camp, David Kuehling wrote:
>>>>>> "Ben" == Ben Martin <monkeyiq at users.sourceforge.net> writes:
>
>> One option would be to ifdef guard the "class" member. This shouldn't
>> break API because it would only come into effect if you are compiling
>> with C++ which is not currently cleanly possible.
>
>> As there are only a handful of "class" members this doesn't really
>> pollute the header too much and you retain full compatibility with
>> your C clients.
>
>Well, why not do 
>
>#ifdef __cplusplus
>    #define class _class
>#endif
>
>At the start of the header file, and
>
>#undef class
>
>at the end?

All these suggestions smell like dirty hacks, I'd just bite the bullet and
make the API change, document it in the ChangeLog and NEWS and bump the
soname.

_______________________________________________
libannodex-dev mailing list
libannodex-dev at lists.annodex.net
http://lists.annodex.net/cgi-bin/mailman/listinfo/libannodex-dev