Summary: | Remove trailing comma in enum | ||
---|---|---|---|
Product: | cairo | Reporter: | Murray Cumming <murrayc> |
Component: | general | Assignee: | Carl Worth <cworth> |
Status: | RESOLVED FIXED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | freedesktop |
Version: | 1.10.3 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | 0001-cairo.h-Remove-a-trailing-comma-from-an-enum.patch |
Description
Murray Cumming
2011-05-09 00:48:57 UTC
Please? (In reply to comment #1) > Please? Pushed. Thank you! commit d0615633dc1529af44740f8326ca1886a8b3bf5c Author: Murray Cumming <murrayc@murrayc.com> Date: Mon May 9 09:45:06 2011 +0200 cairo: Remove trailing comma from cairo_format_t Fixes warnings when building with C++. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=36989 Out of curiosity, is it your C++ compiler that dislikes trailing commas? Because in harfbuzz I'm using C++ and have assumed that trailing commas are harmless. I don't get a warning so far. (In reply to comment #3) > Out of curiosity, is it your C++ compiler that dislikes trailing commas? > Because in harfbuzz I'm using C++ and have assumed that trailing commas are > harmless. I don't get a warning so far. Yes it's g++. We use a higher than normal level of warnings and we enable them as errors during distcheck so we never have them for long. What's the set of flags you use? I personally have an extensive set of compiler warning flags that I use, but cannot find one for trailing comma. Thanks. -pedantic -Wall -Wextra(In reply to comment #5) > What's the set of flags you use? -pedantic -Wall -Wextra I don't know which one turns on this warning. We find them generally useful, though this one is just generally annoying. But I've never given it much thought - I just fix it when I see it. Ah, -pedantic. Thanks. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.