OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

# office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-2450)Precisely-represented Integers not differentiated from Imprecise Integers

• From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
• To: office@lists.oasis-open.org
• Date: Sun, 7 Feb 2010 15:38:15 -0500 (EST)

```
[ http://tools.oasis-open.org/issues/browse/OFFICE-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683#action_17683 ]

Dennis Hamilton commented on OFFICE-2450:
-----------------------------------------

Oh wait!

Andreas, I thought about this some more, and realized that I distracted myself with the existing definition of the Integer Number type.

How does this work for the beginning of 3.10.5:

"""
3.10.5 Integer

A Number type is an Integer Number when the exactly-represented number is a mathematical integer.

Note:

* An exactly-represented number *x* is not a mathematical integer when mathematical floor(*x*) <> ceil(*x*).

* An exactly-represented number *n* is a mathematical integer when mathematical floor(*n*) = ceil(*n*).
"""

I suggest making the two bulleted statements into notes because they are consequences, not definitions.

Is it then safe to observe, in the proposed 3.10.5.1

"""
Note 3. When *n* is a Precise Integer value, the expressions FLOOR(*n*), CEIL(*n*), INT(*n*), ROUND(*n*), and TRUNC(*n*) all have the exact result *n*.
"""

I will update the proposal again once we find agreement.

> Precisely-represented Integers not differentiated from Imprecise Integers
> -------------------------------------------------------------------------
>
>                 Key: OFFICE-2450
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2450
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2 Part 2 CD 1
>         Environment: This issue applies in all OpenFormula drafts through draft-19.
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 Part 2 CD 2
>
>
> The definition of Integer includes a wide range of values that have no fractional part but that are too large to represent integers precisely, there being gaps and even no non-Integer Number values in their vicinity.
> This prevents careful limitation and definition of those functions that require precise integer values to be specified for parameters and to be determined as results.  It also leads to ambiguity and situations such as those illustrated in OFFICE-2209, OFFICE-846, and others invovling specific functions that are only meaningful when precise integer values are involved.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-