Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:63: Extra space before ( in function call [whitespace/parens] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:66: Extra space before ( in function call [whitespace/parens] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:69: Extra space before ( in function call [whitespace/parens] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:69: The parameter name "webView" adds no information, so it should be removed. [readability/parameter_name] [5] Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:73: The parameter name "webView" adds no information, so it should be removed. [readability/parameter_name] [5] Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:73: Extra space before ( in function call [whitespace/parens] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:76: The parameter name "webView" adds no information, so it should be removed. [readability/parameter_name] [5] Source/WebKit2/UIProcess/API/gtk/WebKitWebView.h:76: Extra space before ( in function call [whitespace/parens] [4] These are all false positives.
Created attachment 101994 [details] Patch
Comment on attachment 101994 [details] Patch If possible it would be better to ignore only the headers. This change ignores headers and source files.
(In reply to comment #2) > (From update of attachment 101994 [details]) > If possible it would be better to ignore only the headers. This change ignores headers and source files. There will be false positives in the files too, like code generated from macros like G_DEFINE_TYPE.
(In reply to comment #3) > There will be false positives in the files too, like code generated from macros like G_DEFINE_TYPE. It makes sense to fix those as wel find them as well. I can help out with that.
(In reply to comment #4) > (In reply to comment #3) > > > There will be false positives in the files too, like code generated from macros like G_DEFINE_TYPE. > > It makes sense to fix those as wel find them as well. I can help out with that. what do you mean by fix them? I think we should use gobject macros for maintainability reasons.
(In reply to comment #5) > what do you mean by fix them? I think we should use gobject macros for maintainability reasons. Oh, I mean we can fix the style checker to not complain about G_DEFINE_TYPE lines as well as GObject method names.
(In reply to comment #6) > (In reply to comment #5) > > > what do you mean by fix them? I think we should use gobject macros for maintainability reasons. > > Oh, I mean we can fix the style checker to not complain about G_DEFINE_TYPE lines as well as GObject method names. Ah! that would be awesome :-)
*** This bug has been marked as a duplicate of bug 69481 ***