Hi David,
On Sunday, 2007-02-04 23:43:08 -0500, David A. Wheeler wrote:
> Andreas J Guelzow wrote:
> > > Well, EUROCONVERT(n,source,target) is a 3 argument function in Gnumeric.
> > > (I assume my bias shows when I consider that the measure of all things.)
>
> Excel has:
> > > > Actually it's
> > > > EUROCONVERT(number,source,target,full_precision,triangulation_precision)
>
> Okay, it appears that the 3-parameter version is more portable. So I propose that we call it EUROCONVERT, and that the CONVERT function will have Excel/Gnumeric semantics.
>
> That means that OOo will have to translate its old CONVERT to EUROCONVERT, and its old CONVERT_ADD into CONVERT. Gnumeric and Excel won't need to do much.
I propose three different functions:
- EUROCONVERT with three required and two optional parameters and Excel
semantics for compatibility.
- CONVERT with Excel/Gnumeric semantics, OOo will translate its
CONVERT_ADD into CONVERT.
- CONVERT_UNIT as OOo's general purpose conversion function; may be
mapped by other applications to EUROCONVERT as long as no other
units/currencies are involved.
> In my personal copy I have defined CONVERT, EUROCONVERT, as well as INFO and INDIRECT.
>
> There are a few functions left to do. Anyone willing to pick up one of the last ones left?
I'll first concentrate on a list of other TODOs I identified.
Eike
--
Automatic string conversions considered dangerous. They are the GOTO statements
of spreadsheets. --Robert Weir on the OpenDocument formula subcommittee's list.
