| commit | 277acfe8b38de35be8cb6e274678b5a7919c2d44 | |
| author | Fam Zheng <famz@redhat.com> | |
| Tue, 20 Aug 2013 02:58:21 +0000 (20 10:58 +0800) | ||
| committer | Luiz Capitulino <lcapitulino@redhat.com> | |
| Tue, 20 Aug 2013 15:52:00 +0000 (20 11:52 -0400) | ||
| tree | 9577722ae1bb0ecd9547c95f654b2a0e9a3f548d | treesnapshot (tar.gz zip) |
| parent | 3953e3a5d34fa7caffc3e32eae4270b2d810d966 | commitdiff |
monitor: print the invalid char in error message
It's more friendly to print which char is invalid to user, especially
when user tries to input a float value and expect the monitor to round
it to int. Since we don't round float number when we look for a integer,
telling which char is invalid is less confusing.
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
It's more friendly to print which char is invalid to user, especially
when user tries to input a float value and expect the monitor to round
it to int. Since we don't round float number when we look for a integer,
telling which char is invalid is less confusing.
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
| monitor.c | diffblobblamehistory |