From: Johannes Sixt <j6t@kdbg.org>
To: Marius Ungureanu <marius.ungureanu@xamarin.com>, git@vger.kernel.org
Subject: Re: [PATCH] Updated C# userdiff patterns.
Date: Sat, 26 Apr 2014 09:10:55 +0200 [thread overview]
Message-ID: <535B5BFF.40002@kdbg.org> (raw)
In-Reply-To: <29F78086-81B4-481F-9051-FF3EEBA9BB08@xamarin.com>
Am 26.04.2014 01:25, schrieb Marius Ungureanu:
> New keywords: foreach, break, in, try, finally, as, is, typeof, var,
> default, fixed, checked, unchecked, this, lock, readonly, unsafe,
> ref, out, base, null, delegate, continue.
>
> Removed keywords: instanceof. It's only in Java.
> Moved keywords to happen before modifier parsing, as matching a keyword
> will stop modifiers from being matched.
>
> Added method modifiers: extern, abstract.
>
> Added properties modifiers: abstract.
>
> Added parsing of events and delegates, which are like properties, but
> take an extra keyword.
>
> The reasoning behind adding unsafe to keywords is being also a
> statement that can happen inline in code to mention blocks which are
> unsafe. Also, delegates are not necessarily declared in class bodies,
> but can also happen inline in other functions.
>
> Keywords are based on MSDN docs.
>
> Signed-off-by: Marius Ungureanu <marius.ungureanu@xamarin.com>
Thanks for your contribution.
Please write the commit message in imperative mood, and use full
sentences, not just fragments and avoid contractions ("it's"). Also,
don't capitalize the subject line and drop the full-stop:
update C# userdiff patterns
Add new keywords: foreach, break, ...
Remove keyword instanceof because it is only in Java. ...
BTW, it is now dead easy to add test cases for userdiff patterns. Just
drop files with content like this into t/t4018:
---- t/t4018/csharp-ignore-statement-keywords -----
class Foo {
public int RIGHT()
{
if (x)
else
try
catch (y)
...
ChangeMe;
}
}
-----------------------------------------
(This I just invented, I don't do C#.) See the README file in that
directory.
> ---
> userdiff.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/userdiff.c b/userdiff.c
> index fad52d6..7612c5d 100644
> --- a/userdiff.c
> +++ b/userdiff.c
> @@ -133,14 +133,14 @@ PATTERNS("cpp",
> "|[-+0-9.e]+[fFlL]?|0[xXbB]?[0-9a-fA-F]+[lLuU]*"
> "|[-+*/<>%&^|=!]=|--|\\+\\+|<<=?|>>=?|&&|\\|\\||::|->\\*?|\\.\\*"),
> PATTERNS("csharp",
> - /* Keywords */
> - "!^[ \t]*(do|while|for|if|else|instanceof|new|return|switch|case|throw|catch|using)\n"
> /* Methods and constructors */
> - "^[ \t]*(((static|public|internal|private|protected|new|virtual|sealed|override|unsafe)[ \t]+)*[][<>@.~_[:alnum:]]+[ \t]+[<>@._[:alnum:]]+[ \t]*\\(.*\\))[ \t]*$\n"
> - /* Properties */
> - "^[ \t]*(((static|public|internal|private|protected|new|virtual|sealed|override|unsafe)[ \t]+)*[][<>@.~_[:alnum:]]+[ \t]+[@._[:alnum:]]+)[ \t]*$\n"
> + "^[ \t]*(((abstract|extern|internal|new|override|private|protected|public|sealed|static|unsafe|virtual)[ \t]+)*[][<>@.~_[:alnum:]]+[ \t]+[<>@._[:alnum:]]+[ \t]*\\(.*\\))[ \t]*$\n"
> + /* Properties, events, delegates */
> + "^[ \t]*(((abstract|internal|new|override|private|protected|public|sealed|static|unsafe|virtual)[ \t]+)*((delegate|event)[ \t]+)*[][<>@.~_[:alnum:]]+[ \t]+[@._[:alnum:]]+)[ \t]*$\n"
> /* Type definitions */
> - "^[ \t]*(((static|public|internal|private|protected|new|unsafe|sealed|abstract|partial)[ \t]+)*(class|enum|interface|struct)[ \t]+.*)$\n"
> + "^[ \t]*(((abstract|internal|new|override|partial|private|protected|public|sealed|static|unsafe)[ \t]+)*(class|enum|interface|struct)[ \t]+.*)$\n"
> + /* Keywords */
> + "!^[ \t]*(as|base|break|case|catch|checked|continue|default|delegate|do|else|finally|fixed|for|foreach|if|in|is|lock|new|null|out|readonly|ref|return|switch|this|throw|try|typeof|unchecked|unsafe|using|var|while)\n"
> /* Namespace */
> "^[ \t]*(namespace[ \t]+.*)$",
> /* -- */
Here, you are moving keywords down, but in the commit message you say
that you "moved keywords to happen before modifier parsing". Aren't you
moving keywords *after* something? (Where the "modifiers" are here is
not obvious, but that can be attributed to that I don't do C#.)
BTW, I appreciate that you re-arrange keywords alphabetically. Could you
do that in the commit message, too?
-- Hannes
next prev parent reply other threads:[~2014-04-26 7:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 23:25 [PATCH] Updated C# userdiff patterns Marius Ungureanu
2014-04-26 7:10 ` Johannes Sixt [this message]
2014-04-26 9:55 ` Marius Ungureanu
2014-04-26 10:49 ` Marius Ungureanu
2014-04-26 17:49 ` Johannes Sixt
2014-04-26 18:33 ` Marius Ungureanu
2014-04-26 18:50 ` Johannes Sixt
2014-04-26 18:52 ` Marius Ungureanu
2014-04-27 13:43 ` Marius Ungureanu
2014-04-27 13:45 ` [PATCH 1/2] update " Marius Ungureanu
2014-04-27 13:48 ` [PATCH 2/2] add csharp userdiff tests Marius Ungureanu
2014-04-27 13:47 ` Marius Ungureanu
2014-04-27 16:19 ` Johannes Sixt
2014-04-27 16:46 ` Marius Ungureanu
2014-04-27 20:12 ` Johannes Sixt
2014-04-27 17:11 ` Marius Ungureanu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=535B5BFF.40002@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=marius.ungureanu@xamarin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).