Public Comment: [office-formula] Domain problems with exponential operator and functionPOWER

    • Hide

      1) Move the statement of the allowed values of 0^0 from the definition of the ^ operator in 5.4.6 to the semantics statement in the definition of POWER() in 5.16.46.

      2) We should add the following semantic constraints to POWER():

      a) POWER(0,0) is implementation-defined, but shall be one of 0,1, or an Error
      b) POWER(0,b), where b < 0, shall return an error.
      c) POWER(a,b), where a<=0 and INT(b)!=b, is implementation defined.

      Show
      1) Move the statement of the allowed values of 0^0 from the definition of the ^ operator in 5.4.6 to the semantics statement in the definition of POWER() in 5.16.46. 2) We should add the following semantic constraints to POWER(): a) POWER(0,0) is implementation-defined, but shall be one of 0,1, or an Error b) POWER(0,b), where b < 0, shall return an error. c) POWER(a,b), where a<=0 and INT(b)!=b, is implementation defined.
    • Hide

      Removed 0^0 statement from operator ^.

      Added to Semantics of POWER:

      POWER(0,0) is implementation-defined, but shall be one of 0,1, or an Error.
      POWER(0,b), where b < 0, shall return an error.
      POWER(a,b), where a<=0 and INT(b)!=b, is implementation-defined.

      Show
      Removed 0^0 statement from operator ^. Added to Semantics of POWER: POWER(0,0) is implementation-defined, but shall be one of 0,1, or an Error. POWER(0,b), where b < 0, shall return an error. POWER(a,b), where a<=0 and INT(b)!=b, is implementation-defined.

      Copied from office-comment list

      Original author: Regina Henschel <rb.henschel@t-online.de>
      Original date: 15 Apr 2009 10:17:12 -0000
      Original URL: http://lists.oasis-open.org/archives/office-comment/200904/msg00023.html

            Assignee:
            Robert Weir (Inactive)
            Reporter:
            Robert Weir (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: