On Thu, Feb 21, 2013 at 9:12 PM, Andrew Douglas Pitonyak <and...@pitonyak.org> wrote: > > During the long painful discussion of 0^0, there was mention of creating a > compatibility function for POWER(x,y) to match the behavior in Excel. My > understanding of how this would work is as follows. > > 1. Create another function such as POWER.OTHER(x,y) that behaves as desired. > 2. When an Excel file is read, every instance of POWER is replaced with > POWER.OTHER. > 3. When an Excel file is written, every instance of POWER.OTHER is converted > back to POWER. >
A simpler solution, if you already know that you are reading an Excel file, is to keep the function name, but change the behavior to mimic what Excel does. So a compatibility mode rather than a different function. If we do that, then that would eliminate most of the complexities that you mention below. -Rob > OK, so far so good, I think that I understand how that would work. But, this > does leave a few questions in my mind. > > (Q) Is a user able to use POWER.OTHER inside of Calc? > > (Q) When saved as an ODS file, certainly we don't want to write POWER.OTHER > because then it is using a nonstandard function that will not be used > anywhere else and can only be read by AOO. In other words, I assume that we > would always write POWER rather than POWER.OTHER and the only way to retain > the behavior is to save the file as an excel file or to mess with user > defined attributes while writing the file. > > -- > Andrew Pitonyak > My Macro Document: http://www.pitonyak.org/AndrewMacro.odt > Info: http://www.pitonyak.org/oo.php >
