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

usResourceCompiler needs a verbose option #55

Closed
karthikreddy09 opened this Issue Nov 12, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@karthikreddy09
Contributor

karthikreddy09 commented Nov 12, 2015

In the current implementation the only way to see some output in the terminal when the resource compiler is run, is by rebuilding the tool with preprocessor flag DEBUG_TRACE set. A command line option "-v" would be helpful.

@karthikreddy09 karthikreddy09 self-assigned this Nov 12, 2015

@saschazelzer

This comment has been minimized.

Show comment
Hide comment
@saschazelzer

saschazelzer Jan 14, 2016

Member

This sounds like a useful addition. Since -v is often associated with version information, what do you think about -V for verbose and -VV for "extra" verbose, e.g. including "debug" output?

Member

saschazelzer commented Jan 14, 2016

This sounds like a useful addition. Since -v is often associated with version information, what do you think about -V for verbose and -VV for "extra" verbose, e.g. including "debug" output?

@karthikreddy09

This comment has been minimized.

Show comment
Hide comment
@karthikreddy09

karthikreddy09 Mar 3, 2016

Contributor

I like the idea of verbose levels in general but I think it is an overkill for this tool right now. The single verbose mode fits the need and if there is a requirement in the future to classify the messages, we can consider the very-verbose mode as an enhancement.

Also, with different levels of verbosity we do need guidelines on how to classify the log messages.

I will change the verbose mode short name to "-V" instead of "-v".

Contributor

karthikreddy09 commented Mar 3, 2016

I like the idea of verbose levels in general but I think it is an overkill for this tool right now. The single verbose mode fits the need and if there is a requirement in the future to classify the messages, we can consider the very-verbose mode as an enhancement.

Also, with different levels of verbosity we do need guidelines on how to classify the log messages.

I will change the verbose mode short name to "-V" instead of "-v".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment