Re: Motion to finalise interval literals

[Ned Nedialkov <nedialk@xxxxxxxxxxx>]

On Jun 14, 2013, at 11:54 AM, Richard Fateman wrote:

On 6/14/2013 7:58 AM, Ned Nedialkov wrote:

Dear All, 

I strongly believe text2interval and interval2text must be present. Below is an example from my experience. 

It is *really annoying* when two package produce output in different formats, when 

everything else is the same. 

I hope the above is convincing that having standardized conversion functions is a must.

Actually, I do not find this convincing.  If you have a program VNODE-LP, that is supposed to work on
various computers and with various underlying pieces of software e.g. FILIB++ and PROFIL,
and VNODE-LP produces different answers (or the same answers but in different formats),
to the extent that it matters to you,
then VNODE-LP was not properly "ported" to these different environments.

Well, I do in C++ something like 

cout << a << endl;

where a is an interval. The operator << is overloaded in both FILIB++ and PROFIL.

Ned

In fact, I would expect that VNODE-LP  could extract the inf and sup values from intervals
computed by FILIB++ and PROFIL, and present them in a uniform manner, if the issue were
raised to the appropriate level of concern to the program author.

I agree with you.

Ned