Message ID | 20181101005330.19692-1-gabriel@inconstante.eti.br |
---|---|
State | New |
Headers | show |
Series | [1/2] Fix typo in the documentation of gcvt | expand |
On Wed, 31 Oct 2018, Gabriel F. T. Gomes wrote: > I wasn't sure if this counts as a trivial fix per our rules [1]. The > rules explicitly state that fixing a spelling or grammatical error > counts as a trivial fix, but they do not state anything about typos. > If this commit could be considered a trivial fix, I will also update > the wiki. This fix should be considered obvious.
On Thu, 01 Nov 2018, Joseph Myers wrote: >On Wed, 31 Oct 2018, Gabriel F. T. Gomes wrote: > >> I wasn't sure if this counts as a trivial fix per our rules [1]. The >> rules explicitly state that fixing a spelling or grammatical error >> counts as a trivial fix, but they do not state anything about typos. >> If this commit could be considered a trivial fix, I will also update >> the wiki. > >This fix should be considered obvious. Thanks, this patch is now committed and the wiki is updated.
diff --git a/manual/arith.texi b/manual/arith.texi index 5e123c3ccd..5080abf063 100644 --- a/manual/arith.texi +++ b/manual/arith.texi @@ -3078,7 +3078,7 @@ to @code{fcvt}. @c gcvt calls sprintf, that ultimately calls vfprintf, which malloc()s @c args_value if it's too large, but gcvt never exercises this path. @code{gcvt} is functionally equivalent to @samp{sprintf(buf, "%*g", -ndigit, value}. It is provided only for compatibility's sake. It +ndigit, value)}. It is provided only for compatibility's sake. It returns @var{buf}. If @var{ndigit} decimal digits would exceed the precision of a