Re: [commit] fix for "info threads" printing multiple headers

Pedro Alves
2011-02-22T18:48:39Z

On Tuesday 22 February 2011 18:36:26, Michael Snyder wrote:
> Seems like it would only be useful if the function had to be thread safe.

No, it's useful when something like this happens:

get_number_or_range("1-10", ...);
...
(in_range is left set)
...
QUIT or something like that that breaks the loop.

(new command invocation, with different arg, which happens
to be malformed, for being negative)

get_number_or_range("-1", ...);

Returns 2 instead of throwing an error, which would be
the correct thing to do.

--
Pedro Alves