-
Notifications
You must be signed in to change notification settings - Fork 8
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
extended control of C/C++ validation #67
Comments
Very interesting! Allowing the user to configure the include paths definitely makes sense. And the approach you describe makes sense and basically matches what is done for the ignoring languages feature. The appending code blocks would be cool. I think that is a decent solution. |
great, this one is a bit trickier than the other issue I've opened in the sense it will need to accumulate from one statement to the other... the ignore of languages is a single step prior to start, it's not tied to the subsequent blocks. Any preferences on how to tackle this? Maybe just a global stack where one pushes and then pops? |
No preferences from my side. I agree that it doesn't seem easy at all. |
Does rstcheck/rstcheck#88 help here? |
Hi,
The current
c_checker()
andcpp_checker()
uses a simple-I. -I..
which will get you some basic tests, but in real world we're often using things likepkg-config --cflags glib-2.0
and the likes to provide definitions and more include paths. Then a way to controlINCLUDE_FLAGS
would be required. I'm not sure how to best provide these extensions in a compatible way so we don't break sphinx, maybe using comments?Eventually allow these to be linked in addition to syntax check:
Likewise, sometimes in tutorial/documentation we split the code into multiple pieces that can't be validated at once. I could work-around that by using an external C/C++ file with include statements, however if we could add a argument to "append to previous block" it would be amazing, allowing things like
rstcheck-mode
with a choice ofnew
,append
andignore
:The text was updated successfully, but these errors were encountered: