Re: [boost] Interfaces Library, a macro less implementation

Hi Joel, Joel de Guzman wrote:

Here's my rationale for the macro-less Interfaces:

1) An interface is supposed to be read a lot of times. It has to be immediately understandable to the human parser. It is not an implementation detail. It is a contract.

I totally agree.

2) I need one that can be parsable by a documentation extraction tool such as Doxygen and Synopsis. This is very important! Interfaces need to be documented.

Well, as far as synopsis is concerned I think it can be trained to understand macros quite well, in particular with its new boost.wave backend. :-) So *that* shouldn't be a reason not to use macros. Regards, Stefan