Re:Re: Re: [boost] [serialization] export macros

From: Robert Ramey (ramey_at_[hidden])
Date: 2004-08-12 22:34:49

>However, this problem is by no means specific to the serialization
>library. Whenever you have a macro that takes a classname you may face
>this issue. One could consider it a (inherent) preprocessor
>shortcoming solved by means of template programming. Therefore the
>preprocessor library or one of the libraries from Boost's Generic
>Programming and Template Metaprogramming sections seem a more natural
>place to me for such a tool. Of course, I don't know if one of the
>authors of these libraries agrees and plans to eventually include such
>a template.

>Since the next release is (hopefully) not long away I'd only mention
>this workaround in the documentation of the export macros. Once the
>release is out and everything has settled down there's time to discuss
>where this template belongs.

>This template requires so few keystrokes that for the time being the
>users that need it can easily provide it themselves. But in order to
>avoid unnecessary bloat of Boost I wouldn't like to see it duplicated
>in several Boost libraries in the end.

Wow a very clear and concise explanation - I'm sold - I'll just tweak the
docs and declare victory.

Robert Ramey