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
Makefile.include: enable verbose asserts with DEVELHELP=2 #16864
Conversation
Verbose asserts can be useful, but I always forget how to enable them. To ease use, add a second level to the `DEVELHELP` option that can be used to enable more 'expensive' helpers.
My gut feeling is that it is not a good idea to change DEVELHELP values from (0,1) to (0,1,2). |
Just for context, is the intention that As for discoverability, I see potential for enhancement -- maybe |
I thought it might be similar to how some tools have multiple levels of verbosity |
ifeq (2, $(DEVELHELP)) | ||
CFLAGS += -DDEBUG_ASSERT_VERBOSE | ||
endif |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about as a first step add
ifeq (2, $(DEVELHELP)) | |
CFLAGS += -DDEBUG_ASSERT_VERBOSE | |
endif | |
DEBUG_ASSERT_VERBOSE ?=0 | |
ifeq ($(DEBUG_ASSERT_VERBOSE),1) | |
CFLAGS += -DDEBUG_ASSERT_VERBOSE | |
endif |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would already be quite helpful. Maybe even a shorter name, e.g. VERBOSE_ASSERT
or ASSERT_VERBOSE
, as this is often typed by hand?
closed in favor of #16884 |
Contribution description
Verbose asserts can be useful, but I always forget how to enable them.
To ease use, add a second level to the
DEVELHELP
option that can be used to enable more 'expensive' helpers.Testing procedure
Issues/PRs references