diff options
author | bloodstalker <thabogre@gmail.com> | 2020-04-21 16:51:50 +0000 |
---|---|---|
committer | bloodstalker <thabogre@gmail.com> | 2020-04-21 16:51:50 +0000 |
commit | dbbbb3eebcb99116b9afd768967e7492882737a9 (patch) | |
tree | b312d577582141efa1e735f663ed5fc5e6cec217 /README.md | |
parent | removed the debug prints. boost is no longer a dependency. (diff) | |
download | cgrep-dbbbb3eebcb99116b9afd768967e7492882737a9.tar.gz cgrep-dbbbb3eebcb99116b9afd768967e7492882737a9.zip |
work in progress
Diffstat (limited to '')
-rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -21,9 +21,9 @@ and it will match your regex against all function declarations, and will output ## Features -* It's basically Clang regexing it's way through your C-family source-code. You have all the context you can ever need. -* Can output whether to print the declaration of a match even if the match itself is not a declaration along with the matched result. -* Can output matches in a script-friendly format which could be used in turn by a secondary script. + * It's basically Clang regexing it's way through your C-family source-code. You have all the context you can ever need. + * Can output whether to print the declaration of a match even if the match itself is not a declaration along with the matched result. + * Can output matches in a script-friendly format which could be used in turn by a secondary script. ### Will cgrep try to implement all of the grep switches? The answer is no. The main distinction is that `cgrep` is only meant to work on C-family source files not text files. Most of `grep`'s switches don't apply to the usecase or provide almost no benefits at all.<br/> |