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] Created: (OFFICE-2345) 3.6 Error: Definingerror?

3.6 Error: Defining error?

                 Key: OFFICE-2345
                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2345
             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
          Issue Type: Bug
            Reporter: Patrick Durusau

The first paragraph of 3.6 Error reads:

"An error is one of a set of possible error values. Implementations may have many different error values, but one error value in particular is distinct: #N/A, the result of the NA() function. Users may choose to enter some data values as #N/A, so that this error value propagates to any other formula that uses it, and may test for this using the function ISNA()."

Err, do we mean to define the error #N/A and that it propagates? 

The reason I ask is that here we start off saying that an error is a set of possible error values but don't say what that set is. Moreover it comes up in the next paragraph one or more error results that show up in a result. 

I saw the note about "maximum flexibility" but how would an evaluator know when it saw an error if we don't define it? Or do we want to say that errors, other than #N/A are implementation defined? 

Are there any cases where functions or operators don't return an error value as a result when the error is an input value? 

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]