Thread Links			Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Re: Motion 8: Exception Handling for Interval Arithmetic

To: "Corliss, George" <george.corliss@xxxxxxxxxxxxx>
Subject: Re: Motion 8: Exception Handling for Interval Arithmetic
From: Arnold Neumaier <Arnold.Neumaier@xxxxxxxxxxxx>
Date: Thu, 17 Sep 2009 12:57:29 +0200
Cc: Nate Hayes <nh@xxxxxxxxxxxxxxxxx>, "STDS-1788@xxxxxxxxxxxxxxxxx" <STDS-1788@xxxxxxxxxxxxxxxxx>
Delivered-to: mhonarc@xxxxxxxxxxxxxxxx
In-reply-to: <C6D6D44D.CA91%George.Corliss@xxxxxxxxxxxxx>
List-help: <http://listserv.ieee.org/cgi-bin/wa?LIST=STDS-1788>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO%20STDS-1788>
List-owner: <mailto:STDS-1788-request@LISTSERV.IEEE.ORG>
List-subscribe: <mailto:STDS-1788-subscribe-request@LISTSERV.IEEE.ORG>
List-unsubscribe: <mailto:STDS-1788-unsubscribe-request@LISTSERV.IEEE.ORG>
Organization: University of Vienna
References: <C6D6D44D.CA91%George.Corliss@xxxxxxxxxxxxx>
Sender: stds-1788@xxxxxxxx
User-agent: Thunderbird 2.0.0.23 (X11/20090817)

Corliss, George wrote:


Is it the intent that eventually decorations will be defined in the standard, or are decorations application-defined?

I think of situations in which I'd like to track open/closed for each endpoint, in part to avoid evaluation at known singular endpoints.


I think we should require a minimal set of decoration trits, and mention

further potentially useful ones. Concrete implementations are of coursefree to have more than those required and/or suggested.


Arnold Neumaier

References:
- Re: Motion 8: Exception Handling for Interval Arithmetic
  - From: Corliss, George

Prev by Date: Re: MidRad -- and Two Different Application Domains (TDAD).
Next by Date: Re: Motion 6
Previous by thread: Re: Motion 8: Exception Handling for Interval Arithmetic
Next by thread: Motion P1788/M0008.01_Exception_Handling: Discussion Period Begins.
Index(es):
- Date
- Thread