diff options
author | Andrew Certain <certain@amazon.com> | 2012-12-04 13:33:24 -0800 |
---|---|---|
committer | Scott Feldman <sfeldma@cumulusnetworks.com> | 2013-01-07 09:59:51 -0800 |
commit | 7798b6321cd0c6281b1a119ac894ff3749e88cc1 (patch) | |
tree | 2be0e1ed9af8a9fdf156d013287c154cb081965a /HACKING.pending | |
parent | f92c57f8ba4f1e856934ec1736be3cad62be4785 (diff) |
lib: Changes to VTY string-parsing macros to remove warnings
The VTY_GET_INTEGER_RANGE macro was being used also just to check the range
on a variable that wasn't used (for the "no" version of a VTY command), so I
split the macro into two. Also, since the variable is unsigned, if MIN is
zero, you get a warning about comparing an unsigned number against 0, giving
rise to slightly convoluted logic. Note that the previous two patches were
found by the -Wtype-limits and -Wunused-variables warnings. Without the
changes to these macros, these warnings are triggered erroneously, making it
harder to find the real problems.
Signed-off-by: Scott Feldman <sfeldma@cumulusnetworks.com>
Diffstat (limited to 'HACKING.pending')
0 files changed, 0 insertions, 0 deletions