gmp 6.2.0 documentation bug

2020-09-29 Thread TonyMcC 

Hi,

I think there is a word (a function name?) missing from the 
documentation for gmp 6.2.0.  In gmp.texi, at line 2541 it reads:


"it's probably best to call to get a starting point and iterate from there."

Should there be a function name after "call"?

Best wishes,
Tony
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs

Re: gmp 6.2.0 documentation bug

2020-09-29 Thread Marco Bodrato 

Ciao,

Il 2020-09-29 16:09 TonyMcC ha scritto:

I think there is a word (a function name?) missing from the
documentation for gmp 6.2.0.  In gmp.texi, at line 2541 it reads:

"it's probably best to call to get a starting point and iterate from 
there."


Should there be a function name after "call"?


The complete sentence is:

Functions like @code{mpz_fac_ui}, @code{mpz_fib_ui} and 
@code{mpz_bin_uiui}
are designed for calculating isolated values.  If a range of values is 
wanted
it's probably best to call to get a starting point and iterate from 
there.


Maybe we can simply remove "to call".

The documentation of mpz_fib_ui correctly suggests the function to call: 
mpz_fib2_ui.


Speaking about mpz_fac_ui and mpz_bin_uiui, it shouldn't be necessary to 
suggest how to get the starting point.


Ĝis,
m
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs

Re: gmp 6.2.0 documentation bug

2020-09-29 Thread Paul Zimmermann 
   Hi Tony,

> I think there is a word (a function name?) missing from the 
> documentation for gmp 6.2.0.  In gmp.texi, at line 2541 it reads:
> 
> "it's probably best to call to get a starting point and iterate from there."
> 
> Should there be a function name after "call"?

yes, I guess you should read "it's probably best to call them to get a
starting point and iterate from there" where "them" refers to mpz_fac_ui,
mpz_fib_ui and mpz_bin_uiui.

Paul
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs