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] Commented: (OFFICE-2585) Pseudotypes and thereturn of errors

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

David Wheeler  commented on OFFICE-2585:

A pseudotype is not a type.  Spreadsheets store values that have *types*.  "Pseudotype" is just a "subtype" or "a type that meets some additional constraints".  E.G., an "Integer" is a pseudotype of Number; it is a Number that has no fractional part.  The only reason pseudotypes are in the specification is that I and some others think they make the specification easier to write and understand.

Perhaps we should change the name from "Pseudotype" to "Subtype"?  Would that help?

"If a value doesn't meet the requirements for the pseudotype, what result could there be other than error?"

In many cases, a function can implement capabilities beyond what is required by the specification.  For example, a "factorial" function when given a non-integer value could call on a gamma function to produce something useful.  We are specifying the *minimum* requirements... if you ask an evaluator to do something beyond what is required, then it is no longer portable, but that does not make it meaningless.

> Pseudotypes and the return of errors
> ------------------------------------
>                 Key: OFFICE-2585
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2585
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>            Reporter: Patrick Durusau
> In 5.2, under Semantics we say: "If a parameter is a pseudotype, but the provided value fails to meet the requirements for that type, a function/operator may return an Error value."
> If a value doesn't meet the requirements for the pseudotype, what result could there be other than error? 
> If there are different results, how does this "standard" enable interoperability? 

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]