aboutsummaryrefslogtreecommitdiff
path: root/grep.c
diff options
context:
space:
mode:
authorThomas Rast <trast@student.ethz.ch>2010-12-18 17:17:54 +0100
committerJunio C Hamano <gitster@pobox.com>2011-01-18 08:51:58 -0800
commit8d96e7288f2be9de6d09352dc445f18f89564500 (patch)
tree664c85e92832fbb8f10b8af2c4efddea224b75af /grep.c
parentadf872e7837cc92e390f00ee32f32c5639d3a444 (diff)
downloadgit-8d96e7288f2be9de6d09352dc445f18f89564500.tar.gz
git-8d96e7288f2be9de6d09352dc445f18f89564500.tar.xz
t4034: bulk verify builtin word regex sanity
The builtin word regexes should be tested with some simple examples against simple issues. Do this in bulk. Mainly due to a lack of language knowledge and inspiration, most of the test cases (cpp, csharp, java, objc, pascal, php, python, ruby) are directly based off a C operator precedence table to verify that all operators are split correctly. This means that they are probably incomplete or inaccurate except for 'cpp' itself. Still, they are good enough to already have uncovered a typo in the python and ruby patterns. 'fortran' is based on my anecdotal knowledge of the DO10I parsing rules, and thus probably useless. The rest (bibtex, html, tex) are an ad-hoc test of what I consider important splits in those languages. Signed-off-by: Thomas Rast <trast@student.ethz.ch> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'grep.c')
0 files changed, 0 insertions, 0 deletions