Le 28/02/2018 à 23:32, Junio C Hamano a écrit :
> Eric Sunshine writes:
>
>> On Wed, Feb 28, 2018 at 5:17 PM, Alban Gruin wrote:
>>> Yes, but I can split the line like that:
>>>
>>> % cat >baz.go<<\EOF
>>> package baz
>>> func baz(arg1
Eric Sunshine writes:
> On Wed, Feb 28, 2018 at 5:17 PM, Alban Gruin wrote:
>> Yes, but I can split the line like that:
>>
>> % cat >baz.go<<\EOF
>> package baz
>> func baz(arg1 int64,
>> arg2 int64) {
>> }
>> EOF
>>
On Wed, Feb 28, 2018 at 5:17 PM, Alban Gruin wrote:
> Yes, but I can split the line like that:
>
> % cat >baz.go<<\EOF
> package baz
> func baz(arg1 int64,
> arg2 int64) {
> }
> EOF
> % go build baz.go
>
> This complies to the standard
Le 28/02/2018 à 23:00, Eric Sunshine a écrit :
> On Wed, Feb 28, 2018 at 4:31 PM, Alban Gruin wrote:
diff --git a/userdiff.c b/userdiff.c
@@ -38,6 +38,15 @@ IPATTERN("fortran",
+PATTERNS("golang",
+/* Functions */
+"^[ \t]*(func[
On Wed, Feb 28, 2018 at 4:31 PM, Alban Gruin wrote:
>>> diff --git a/userdiff.c b/userdiff.c
>>> @@ -38,6 +38,15 @@ IPATTERN("fortran",
>>> +PATTERNS("golang",
>>> +/* Functions */
>>> +"^[ \t]*(func[ \t]*.*(\\{[ \t]*)?)\n"
>>
>> Why is the brace (and
>> diff --git a/userdiff.c b/userdiff.c
>> @@ -38,6 +38,15 @@ IPATTERN("fortran",
>> +PATTERNS("golang",
>> +/* Functions */
>> +"^[ \t]*(func[ \t]*.*(\\{[ \t]*)?)\n"
>
> Why is the brace (and possible following whitespace) optional?
> Considering that the language demands that
On Wed, Feb 28, 2018 at 12:29 PM, Alban Gruin wrote:
> This adds xfuncname and word_regex patterns for golang, a quite
> popular programming language. It also includes test cases for the
> xfuncname regex (t4018) and an updated documentation.
s/an //
> The xfuncname regex
This adds xfuncname and word_regex patterns for golang, a quite
popular programming language. It also includes test cases for the
xfuncname regex (t4018) and an updated documentation.
The xfuncname regex finds functions, structs and interfaces. The
word_regex pattern finds identifiers, integers,
8 matches
Mail list logo