[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53167] format long doesn't adjust precision t

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #53167] format long doesn't adjust precision to 7 digits when displaying single() values
Date: Mon, 19 Feb 2018 19:39:14 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #7, bug #53167 (project octave):

Another reason for the output_precision variable was to allow more
fine-grained control than just format long or short.  Is it acceptable to drop
that feature?  I'm OK with limiting output to no more than the number of
digits that are meaningful, but it would be nice to maintain the ability to
get, say 10 digits for doubles, not just 8 or 16.

That's why I asked whether there should be just one value of output_precision,
and then limit the actual output to the max number of meaningful digits for
the type.  If we do that and have only one output_precision value, then users
could set output_precision to whatever value and we would impose a limit when
printing.  But if we have separate output_precision values for single and
double, we can limit their ranges at the time they are set from a
user-provided value.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]