[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: Avoiding #warning (C/C++ preprocessor extension)
From:       Sascha Cunz <sascha.cunz () tiscali ! de>
Date:       2005-10-30 22:28:54
Message-ID: 200510302328.54748.sascha.cunz () tiscali ! de
[Download RAW message or body]

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.

Sascha

[prev in list] [next in list] [prev in thread] [next in thread]