Re: [office-formula] EUROCONVERT precision in Gnumeric

Hi,

Maybe this got buried in the thread, but what's the opinion of the
Gnumeric team regarding a change in the precision behavior of the
3 parameter case? Please see below.

On Friday, 2007-03-02 16:14:05 +0100, Eike Rathke wrote:

> > > - EUROCONVERT with three required and two optional parameters and Excel
> > >   semantics for compatibility.
> > 
> No one objected, and as that section was unmodified I changed it
> accordingly when I came across. The different behavior though with and
> without 4th parameter (FullPrecision) being supported may be unexpected.
> FullPrecision says how to treat the result, True == full precision,
> False == round to currency dependent decimals, with a default of False.
> However, applications not supporting that parameter may tend to return
> the full precision result, implying a default of True there.


Here's the relevant part:

> As Gnumeric currently is the only application having a EUROCONVERT
> function: would the Gnumeric developers be willing to either support the
> additional 2 optional parameters, or change their 3 parameter version to
> return a result as if a FullPrecision=False was given?
> 
> Otherwise we'd have to state in the spec that, depending on the
> application, one may or may not get a rounded result, which isn't really
> user friendly..


Thanks
  Eike

-- 
Automatic string conversions considered dangerous. They are the GOTO statements
of spreadsheets.  --Robert Weir on the OpenDocument formula subcommittee's list.