Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

case sensitivity of warning message (Origin: bugzilla #621695) #3803

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity enhancement in component general for ---
Reported in version 1.7.0 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2010-06-15 20:34:28 +0000, Craig Lemon wrote:

Created attachment 163723
Warnings as output by doxygen and Visual Studio

I have changed the warn_format to "$file($line) : $text" (without the " characters) to replicate the warning style output by Visual Studio. This is in an attempt to get warning messages output by doxygen to appear in the Error List window of Visual Studio.

Changing the warn_format as above has output in the correct format in the Build Output window, yet these warnings do not appear in the Error List of Visual Studio.

I have noticed that the word warning contains an uppercase W when output by doxydoc, and a lowercase w when output by one of the Visual Studio tasks, so I am thinking that this is the reason why these warnings are not showing up in the Visual Studio Error List.

Attached is a screen shot showing the different warnings as output by 1) doxygen and 2) Visual Studio.

So, the enhancement that I am suggesting here, is to have the ability to output the word warning in a warning message with a lowercase w.

thanks, Craig

On 2010-06-17 13:07:37 +0000, Dimitri van Heesch wrote:

A bit silly that Visual Studio is so inflexible, but I have no problems making the warning and error words lower case in messages.

On 2010-06-25 11:49:02 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.1. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

On 2010-10-09 08:19:45 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.2. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.