check-spacing: do not kill C++-style comments

Our HACKING guide forbids these.
There's no point in exempting these from the spacing check
if their existence is against our coding style.

Note that the non-usage of these comments itself is not enforced
by syntax check, probably because of the need to implement a C parser.

Signed-off-by: Ján Tomko <jtomko@redhat.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>
This commit is contained in:
Ján Tomko committed 2018-11-06 14:14:41 +01:00
1 parent 90dba47a07
commit 912b8a5970
2 files changed
+2 -5

No files matched your search

-3
View File
@@ -45,9 +45,6 @@ foreach my $file (@ARGV) {
# Kill any quoted strings
$data =~ s,"(?:[^\\\"]|\\.)*","XXX",g;
# Kill any C++ style comments
$data =~ s,//.*$,//,;
next if $data =~ /^#/;
# Kill contents of multi-line comments
+2 -2
View File
@@ -230,8 +230,8 @@ virWinsockInit(void)
WSADATA winsock_data;
/* http://msdn2.microsoft.com/en-us/library/ms742213.aspx */
winsock_version = MAKEWORD (2, 2);
err = WSAStartup (winsock_version, &winsock_data);
winsock_version = MAKEWORD(2, 2);
err = WSAStartup(winsock_version, &winsock_data);
return err == 0 ? 0 : -1;
}
#endif