Re: White spaces in numbers: mpz_set_str

[Kevin Ryde]

Gabor Szokoli <address@hidden> writes:
>
> I'd like to cast my vote on the mpz_set_str issue in favor of strict
> processing. A number padded and cut by whitespace characters should
> make this function fail.
>
> You could always provide both mechanisms under separate names for
> those who care, and make the default behave the way it's faster for
> those who don't.

We probably have to leave mpz_set_str alone, for upward compatibility.

We're contemplating adding a parsing function in the style of
"strtol", which would be a better building block.


-- 
All followups to address@hidden please.