6 Commits

Author	SHA1	Message	Date
Robert Schulze	0f6715bd91	Follow-up to PR #37300: semicolon warnings ... In PR #37300, Alexej asked why we the compiler does not warn about unnecessary semicolons, e.g. f() { }; // <-- here The answer is surprising: In C++98, above syntax was disallowed but by most compilers accepted it regardless. C++>11 introduced "empty declarations" which made the syntax legal. The previous behavior can be restored using flag -Wc++98-compat-extra-semi. This finds many useless semicolons which were removed in this change. Unfortunately, there are also false positives which would require #pragma-s and HAS_* logic (--> check_flags.cmake) to suppress. In the end, -Wc++98-compat-extra-semi comes with extra effort for little benefit. Therefore, this change only fixes some semicolons but does not enable the flag.	2022-05-20 15:06:34 +02:00
Raúl Marín	c312121ced	gtest_sensitive_data_masker: Adapt error output after re2 update	2021-05-17 19:38:23 +02:00
Alexander Tokmakov	5cdfcfb307	remove other stringstreams	2020-11-09 22:12:44 +03:00
Alexey Milovidov	941ee1a214	Fix error	2020-11-07 22:02:22 +03:00
Alexey Milovidov	fd84d16387	Fix "server failed to start" error	2020-11-07 03:14:53 +03:00
Ivan Lezhankin	06446b4f08	dbms/ → src/	2020-04-03 18:14:31 +03:00