Opened 10 years ago
Closed 10 years ago
#859 closed defect (fixed)
turn on all warnings when compiling rasdaman
| Reported by: | Dimitar Misev | Owned by: | Dimitar Misev |
|---|---|---|---|
| Priority: | major | Milestone: | 9.0.x |
| Component: | build system | Version: | development |
| Keywords: | Cc: | Peter Baumann | |
| Complexity: | Medium |
Description
We should add a --enable-strict option to the configure script, which will add g++ options that turn on warnings and make them errors that halt compilation.
This option should then be regularly used by developers, once the code is cleaned from current warnings.
Change History (4)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
It's a bad idea from a user's point of view. Even if we fix all warnings on our compiler versions, users may have different (usually newer) that throw new warnings and fail their make. But users usually don't know about the configure option to disable it, so it's not very user-friendly.
I think it's better that developers are aware of it and consciously turn it on.
comment:3 by , 10 years ago
hm, from the perspective of gcc changing behavior more often than one would think this is a good thought indeed. Hence, agreeing with you.
comment:4 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
should we make this behavior default maybe?