> That's right, but as we won't have as many changes to the R5 API it > probably doesn't matter for now; and anyway that's an argument to put > the documentation next to the code, not in the headers - you can't > change the headers (because that would break binary compatibility), but > you can change the implementation at any point, like new return codes > or whatever. But the headers are the 'face' of the API. Secondly, placing Doxygen configuration in the headers prevents a bit of extra work, because some members (or the class itself) don't have to be explicitly mentioned to doxygen. Anyway, as it is already decided, I will refrain from commenting on this. Niels