Re: list of operations for test suite. suggested format
On 2013-04-30 07:44:45 -0700, Richard Fateman wrote:
> On 4/29/13 9:20 PM, Dmitry Nadezhin wrote:
> >How do you want to represent infinitives by triples ?
> the IEEE 754 standard has unambiguous representations for +-oo for
> each base type.
Partly. For portability, one needs to require the lower-case forms.
> >>> 7) Are comments allowed
I'd say that this is a must.
[...]
> >> If you wish to use // or .... # that's OK with me.
> >
> >I think that most people will prefer C++ style comments starting with // .
I'm not so sure. # is used in shell scripts and various languages
such as Perl, Python and Ruby, and also very often in text-based
configuration files. Both forms could be allowed.
FYI: http://en.wikipedia.org/wiki/Comment_%28computer_programming%29
> If an input interval cannot be expressed exactly in the format
> being tested, then the line should be rejected as a test in that format.
> Rounding up/down/widening/ computing (tightest) hull is the essence
> of the computation being tested. If you allow the program to "interpret"
> the test suite by choosing some roundings and hull computations you
> are invalidating the purpose of the test.
I agree.
--
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)