[cfe-dev] Info diagnostic level
Victor Zverovich
victor.zverovich at googlemail.com
Fri Nov 20 22:58:13 PST 2009
The name Remarks is OK for me.
I see one of the uses of this in for the output of progress information, for
example, to report which file is being compiled as VS does. However it can
be seen as a general output facility that uses diagnostic instead of writing
to the stdout.
Therefore I think that this kind of diagnostic unlike errors, warnings or
notes should be output by existing clients with minimal
formatting (without prepending "remark: " or whatever, only the location if
it is specified).
For the same reason I'd say that it shouldn't be counted in the diagnostic
count and should be never turned into
errors with -Werror.
Does it make sense?
Victor
2009/11/20 Douglas Gregor <dgregor at apple.com>
>
> On Nov 20, 2009, at 1:11 AM, Victor Zverovich wrote:
>
> I am actively using the clang's Basic library in my project and in
>> particular its diagnostic part which is great.
>> However it has the following limitation: it is not possible to report an
>> "informational" message which is neither warning nor error through it. While
>> clang doesn't need this functionality it may be useful for other users (me
>> being one of them :)) without any overhead for clang. The attached patch
>> introduces the Info diagnostic level.
>>
>
>
> I'm okay with adding another diagnostic level. Some other compilers have
> "remarks"; I'd slightly prefer that name over "info". However, to include
> your patch in Clang we need to fully integrate this new kind of diagnostic.
> In addition to adding an enumerator to Level, we need to answer a few
> questions:
>
> - How do all of the existing diagnostic clients format infos/remarks?
> - Are infos/remarks counted in the diagnostic count?
> - How do infos/remarks behave w.r.t. -Werror?
>
> - Doug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20091121/3b84efd6/attachment.html>
More information about the cfe-dev
mailing list