386076ec92
The implementation of digit-separating single-quotes introduced a
note-worthy regression: the change of a character literal with a
digit would splice the digit and the closing single-quote. For
example, the change from 'a' to '2' is now tokenized as
'[-a'-]{+2'+} instead of '[-a-]{+2+}'.
The options to fix the regression are:
- Tighten the regular expression such that the single-quote can only
occur between digits (that would match the official syntax).
- Remove support for digit separators.
I chose to remove support, because
- I have not seen a lot of code make use of digit separators.
- If code does use digit separators, then the numbers are typically
long. If a change in one of the segments occurs, it is actually
better visible if only that segment is highlighted as the word
that changed instead of the whole long number.
This choice does introduce another minor regression, though, which
is highlighted in the test case: when a change occurs in the second
or later segment of a hexadecimal number where the segment begins
with a digit, but also has letters, the segment is mistaken as
consisting of a number and an identifier. I can live with that.
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
31 lines
432 B
Plaintext
31 lines
432 B
Plaintext
Foo() : x(0&42) { bar(x.Find); }
|
|
cout<<"Hello World?\n"<<endl;
|
|
(1 +1e10 0xabcdef) '2'
|
|
// long double
|
|
3.141592654e+10l
|
|
// float
|
|
120E6f
|
|
// hex
|
|
0xdeaf'1eaf+7ULL
|
|
// octal
|
|
01234560
|
|
// binary
|
|
0b1100+e1
|
|
// expression
|
|
1.5-e+3+f
|
|
// another one
|
|
str.e+75
|
|
[a] b->*v d.*e
|
|
~!a !~b c+ d- e**f g&&h
|
|
a*=b c/=d e%=f
|
|
a++b c--d
|
|
a<<=b c>>=d
|
|
a<=b c<d e>=f g>h i<=>j
|
|
a!=b c=d
|
|
a^=b c|=d e&=f
|
|
a|b
|
|
a?:b
|
|
a==b c+d e-f g*h i/j k%l m<<n o>>p q&r s^t u|v
|
|
a,b
|
|
a:b
|