RFC: Avoiding #warning (C/C++ preprocessor extension)

Sascha Cunz sascha.cunz at tiscali.de
Sun Oct 30 22:28:54 GMT 2005

On Sunday 30 October 2005 22:49, Adriaan de Groot wrote:
> On Sunday 30 October 2005 21:25, Jarosław Staniek wrote:
> > 1. Preferred way: Using doxygen @todo tag instead of #warning. Then
> > warnings can be accessible:
> The thing about @todo is that it collects lots of different things; not
> just compile warning type messages, but there's lots of @todos about
> ambiguous dox and weird coding. Mixing them together might be confusing.

Then why not add a new "related page" for i.e. "@warning"? Doxygen can do that 
for you without big problems.

> In
> addition, now you don't see the @todos/#warnings during compilation _at
> all_, and you can't use -Wall to catch them. That means you _have_ to look
> at a web page to discover what's still broken in the code.


More information about the kde-core-devel mailing list