Fixes #3092 - Implement loading @file
c arguments
#3178
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for the bug #3092 I filed on expanding
@file
c arguments.Just as background, a
@file
argument works like this: Ifgcc
orclang
encounters a flag which starts with@
it will treat the remainder of that flag as a file path, and it will use the contents of that file as flags. (It is somewhat like an "include file" for command line arguments).Initially I implemented this as simply passing the
@file
arguments directly to the compiler, but then I realized that this could cause problems since the arguments contained with the file would not get parsed and filtered. If you are curious this implementation is here.This PR instead has vim read the contents of the
@file
and will add those to the argument list to be filtered.I have added a Vader test for this.
Thanks for you work!