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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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


Subject: [OASIS Issue Tracker] Updated: (OFFICE-3041) Bit operations, stillsome ambiguity



     [ http://tools.oasis-open.org/issues/browse/OFFICE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Patterson updated OFFICE-3041:
-----------------------------------

      Proposal: 
Update 6.6.1 as follows:

6.6.1	General
Evaluators shall support unsigned integer values and results of at least 48 bits (values from 0 to 2^48-1 inclusive).  Operations that resut in a value that cannot be represented within 48 bits produce a result that is Implementation Defined

  was:
Update 6.6.1 as follows:

6.6.1	General
Evaluators shall support unsigned integer values and results of at least 48 bits (values from 0 to 2^48-1 inclusive).  Operations that resut in a value that cannot be represented within 48 bits may produce a result that is Implementation Defined

    Resolution: 
Update 6.6.1 as follows:

6.6.1	General
Evaluators shall support unsigned integer values and results of at least 48 bits (values from 0 to 2^48-1 inclusive).  Operations that resut in a value that cannot be represented within 48 bits produce a result that is Implementation Defined

> Bit operations, still some ambiguity
> ------------------------------------
>
>                 Key: OFFICE-3041
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3041
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Needs Discussion, OpenFormula
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Eric Patterson
>            Assignee: Eric Patterson
>             Fix For: ODF 1.2 CD 06
>
>
> As part of the fix in http://tools.oasis-open.org/issues/browse/OFFICE-2327, we've set the minimum to 48 bits, but in doing so, there is still ambiguity when doing shift operations.  If implementations have different maximums, you may get different results when shifting outside the range.  
> Assuming the minimum 48-bit support is provided, then BITLSHIFT(1,48) places the 1 in the 49th bit which is outside of the 48-bit range that's supported.  Is that bit lost (producing 0 as a result), or does that produce an error?

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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